The tool should always be chosen according to the task and prior knowledge. If the purpose is to analyze a small shellcode, then standard tools such as objdump may be good enough. Otherwise, it generally makes sense to master more powerful all-in-one solutions that support either multiple architectures or the main architecture of interest. While the learning curve in this case will be much steeper, this knowledge can later be re-applied to handle new tasks and eventually can save an impressive amount of time. The ability to do both static and dynamic analysis in one place would definitely be an advantage as well.
Open source solutions nowadays provide a pretty decent alternative to the commercial ones, so eventually, the decision should be done by the engineer. If money doesn't matter, then it makes sense to try several of them; check which one has the better interface, documentation, and community; and eventually stick to the most comfortable solution.
Finally, if...
