Not sure I understand what human-readable has to do with this.
The naming was used in the same spirit as listHardwareProfiles and listAssignableLocation which are names we already use.

Don't have a strong preference on the name here. Just want to avoid get :-)