Nope. On all counts, really.
A large, well-known multi-national where I live, for example, has in excess of 25,000 GPOs. So, while you may think you have too many GPOs and too much complexity (and you may well), this is not a problem that's really solvable. Large, complex organizations with complex relationships have large, complex directories. No way around it.
The only real solution is proper design, enforcement and administration of your AD structure... which is also not an easy task, or something that's solvable with "a few tools." And, again, even with proper deign and policies in place, you'll end up with a relatively large and complicated AD. It's just the nature of this type of data - there's a lot of it, and it tracks a lot of relationships and dependencies, so it's complex. Nature of the beast.
Your first goal is to decide how you want to organize/design your AD structure and hierarchies, which is a project in and of itself.
Once you've got that settled, you should move on to reporting in your current environment, which is also not a trivial task. There are any number of tools for that, including plain old scripts to query and fetch data over LDAP, as well as third party tools. Quest's Windows and Active Directory Reporting Tools would probably be your "industry standard" you ask about, but they're expensive, and not a silver bullet by any stretch. For example, an AD redesign I did for a ~1,000 employee company, the file permissions report on their file servers generated Excel spreadsheets with over a quarter million lines.
Then, once you've figured out where you want to be, and where you are now, you need to plan out a way to get there. And, of course, this has to be done while the environment's running, because you can't very well take AD offline for a couple months while you sort things out. It's worth noting that this often results in the realization that it's easier and better to stand up a whole new domain or forest that you "migrate" the existing environment to.
Finally, once you've done all that, it's imperative to get polices and procedures in place and enforced to protect the structure and organization of the new and/or cleaned-up AD, otherwise you'll be back in the same mess you started with, in no time flat.
A lot of work.
Depending on the size and degree of disorganization of your AD environment, you may be better off just documenting your AD environment, tackling the low-hanging-fruit and implementing policies as you clean up a particular area. For example, cleaning up group memberships by removing ex-employees and blank groups, and implementing a procedure around employee separations, such as "run the following script to determine group memberships and remove the former employee from all groups."
but anyway you come at it, there's no tool to do it for you, and it's going to require a fair bit of effort to accomplish.