Often the key strength/weakness is the same thing. In other words, a single characteristic can be a strength in one circumstance and a weakness in another.
As an example, UML is a generic modeling tool while ER is a database specific modeling tool. If you want to model OOP classes, that is an advantage for UML. If you want to model databases, that is an advantage for ER.
If you think about this compared to "real world" tools, a jeweler's saw is a very specialized tool, while a chainsaw is a very generic tool. In an abstract sense, the specialized versus generic doesn't matter, they are both saws and it isn't relevant. However, if you want to cut down a tree, the jewler's saw isn't much good... If you want to cut a ring off of your grandmother's swollen finger, the chainsaw probably wouldn't be your first choice either!
If you start to look at the problem from this perspective, you'll probably find some obvious differences between the two (UML and ER), that makes one much better suited for a given task than the other.
-PatP