I agree that the documentation of the Permissions leaves a lot to be desired. I would like to add to your suggestion, a list of what each permission actually allows the user to do. It may seem obvious, but isn't always!
Within the documentation for a particular action, it usually details what permissions are required to perform it, but there isn't an easy way to know what other actions require the permission. So, if you want to stop a user from doing something, you cannot be sure what unexpected side effects of removing it will be! For example, say we want to prevent users from transferring directly to a queue. It would seem that the Routing > Queue > View permission would do the trick, but we cannot be certain that it won't break anything else. The permission is definitely mentioned on the Page discussing transfers, however a search for the permission does not list that page, which casts doubt on how comprehensive the search results are.
I have an idea posted for this and would appreciate any up-votes you feel are worthy.
------------------------------
Paul Simpson
Eventus Solutions Group
------------------------------