Unfortunately, the current situation is that either you need to learn to read legalese (at least well enough to know what you're agreeing to), hire an expert to review it (which is what companies do), deal with companies whom you believe will not abuse your trust (because they've got too much to lose by being stupid about this), or "vote with your feet and your wallet" and decline to do business with the company that asked you to sign something you aren't comfortable with.
Up to you to decide what your time, and your effort, and your trust, are worth.
If companies lose enough business to competetors with simpler licensing agreements, they will consider investing more money in simplifying their agreements.
I'm not sure consumer protection laws can do much to improve legal language, because each license is an individual contract between you and the publisher. Recommendations can be made for standard language -- that's certainly happened in the open-source arena, where folks may use one of the existing well-understood license agreements -- but the more complicated the product, and the more expensive the product, the more likely that the publisher is going to worry about "edge cases" arising and the more custom language is likely to come back in.
After all, if things weren't complicated they wouldn't need license agreements, per se, at all. Copyright SHOULD cover most of the common cases. But as soon as you get into "can I install this on more than one machine" and "can I let others use it remotely" and other things that people want to do with software that they can't do with a physical book, life starts to get messy.