Scope names must be machine-readable and thus, it "must only contain lowercase letters, numbers, underscores, and colons" to quote the scope entity form.
This makes for a less than ideal user experience when selecting a scope on the consumer form:
Since we already have a scope description with a human-readable text string, use that as the option label:
Review MR.
Human-readable descriptions are shown for scope reference fields instead of the machine-readable names.
None.
None, the submitted values are still the names.
Needs work
6.0
User interface
I don't think the description is the right property to use, it's purpose is to describe the scope, which can be lengthy. It would be more fitting to introduce a new property e.g. label.