stop_motor

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

Annotations already mark the operation as mutating, idempotent, and non-destructive. The description adds meaningful context by explaining that enabling brake means the motor actively holds its position, which is behavioral information not present in the schema or annotations. It does not contradict the annotations.

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 a single, front-loaded sentence with no filler. Every phrase earns its place: it names the action, the target, and the optional braking behavior.

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?

For a simple two-parameter tool with clear annotations and an enum-driven schema, the description covers the core action and the key optional behavior. It could be more explicit about what happens when brake is false, but the schema default and the phrase 'optionally actively holding' make the intended behavior reasonably clear.

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?

Schema description coverage is 0%, so the description must compensate for both parameters. It only clarifies 'brake' through the phrase 'actively holding its position'; the 'port' parameter is not mentioned at all and relies entirely on the schema enum.

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 starts with the specific verb 'Stop' and a singular resource, 'one motor', which clearly distinguishes it from sibling stop_motors. The phrase 'optionally actively holding its position' also explains the brake behavior in plain terms.

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?

The description gives no explicit guidance on when to use this tool instead of stop_motors, emergency_stop, or other motor-related siblings. The only usage hint is implied by the singular 'one motor' and the optional brake flag.

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