Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must compensate. It does not explain the four parameters (guildId, positions, dryRun, reason) beyond implying that 'positions' relates to role ordering. The phrase 'bulk reorder' provides minimal semantic value, but without explicit clarification, agents cannot reliably construct correct calls.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.