Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is reported as 0% at the top level, but the description documents the key semantic parameters: idType enum values with examples, idValue, and exchCode usage. It compensates well for the schema, though it doesn't cover the many fin-specific params (wholesaler_ids, source_resource_id, etc.) which appear irrelevant/copied and undocumented.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.