Not to me. I have lots of data exchanging going on where the format is expressed well in XSD and in JSON Schema it is expressed through documentation, code, and a history of angry emails.

If it can't be expressed as a JSON schema, it's a bad idea. If it can be expressed by a JSON schema, it may be a good idea.

This does not match my experience.

Can you provide some clear explanation or examples of why having less power to express a schema is desirable?

Paralysis of choice.

This remains an unconvincing argument.

Not everybody needs convincing. JSON already won.

It won in places where one does not need to express an integer larger than 2^53. Lots of us have harder requirements.