You mention "Tools", did you mean "Software Tools". And, you have to use a decompiler.
I think, "Reviewing", in this case, means more like guidelines & I.T. (rules) policies.
Things, you may want to consider:
* Does a library provides source code ? (No Source Code, preferably, avoided) If you have to pay a extra, for the source code, then choose no library, or pay for the source code, but, dont buy propertary libraries without source code or support.
* Does a library is for a particular programming language or programming enviroment, or several ?
If it's for several programming languages, make sure can be compiled, loaded, or integrated to other languages.
* Does a library provides documentation, both, as files, and web ?
I have deal with several libraries whom lack one or another. Don't trust a library that doesn't have files independent of web. There are many great software libraries, where it only has web documentation. When a winter storm arrives,say "good bye" Internet, and say "good bye" to documentation. The same goes if a hacker or virus attack the documentation server, or a technical malfunction at the network or server.
Web documentation is good, because sometimes its updated regularly. But, don't count to have available all time. Some developers just take the comments of the source code & generate both, we pages, & local files. And, sometimes, this is helpful.
* Does a third party library provides support ?
The answer is similar to the previous answer. Open & Free Software can be great, but, sometimes, lacks this, because, many developers cannot provide full time support. (Unless paid by companies or groups like Apache or Google ).
* Does a third party library provides an A.P.I., or its structured. ?
A good software can be difficult to integrate with other software if its not structured, by classes, modules, or functions.
Just my [spartan] 2 silver cents [coins].