The schema, not comments, should be the canonical place to find ‘readOnly’ and ‘deprecated’ status

I’m working with the Android Management API and I notice that a couple fields have ‘readOnly’ status, but many fields that are read only are not so annotated. And there is no use of the ‘deprecated’ annotation at all anywhere in the schema.
It’s great that these states are called out in the comments (well, better than nothing), the whole point of a json-schema is for all the attributes of an API be machine readable. Please consider making both ‘readOnly’ and ‘deprecated’ mandatory annotations in your schemas for fields that are read only or deprecated.

See https://json-schema.org/understanding-json-schema/reference/generic.html info about draft 7 and draft 2019-09

Start by reviewing the repository’s schemas for the Android Management API and the referenced JSON Schema draft 7 and draft 2019-09 documentation. The work is done when fields that are read-only or deprecated are consistently represented with machine-readable readOnly or deprecated annotations rather than comments alone.

Written by the indexing model from the issue text.