get_motor_output_reordering

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Without annotations, the description should disclose behavior. It states reordering happens 'without rewiring', but does not mention side effects, required conditions, or the inconsistency between described parameters and empty schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short but includes a redundant title and a parameter hint that conflicts with the schema. It could be restructured to clarify the parameter issue.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (motor output reordering is a significant operation), the lack of output schema, annotations, and the contradictory parameter mention make the description incomplete and confusing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description implies parameters (output indices) but the schema declares zero properties. This contradiction undermines semantic clarity. Schema coverage is 100% only because there are no properties, so the description adds no valid parameter meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description claims the tool reorders motor output channels, but contradicts itself by mentioning parameters ('Specify the output index') while the input schema has no properties. This makes the purpose unclear.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool or distinguish it from siblings. The description does not address contexts or alternatives among the many get/set tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.