hyper-schema.json has descriptions for its fields. json.schema does not. We should pick one or the other appraoch.

In favor of descriptions:

• It makes the meta-schema something of a quick-ref guide

Problems with descriptions:

• Easily get out of sync with the specification
• Long strings are annoying in JSON, but short descriptions can leave out important parts while giving a false sense of security to people who do not read the actual spec or longer tutorials.

I prefer no descriptions, but I'd be OK with adding descriptions everywhere.