stop

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

With no annotations, the description informs that the action is immediate ('Immediately halt motion') and that it is always available, implying no special permissions or destructive side effects beyond stopping.

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?

Two sentences: first states action, second provides usage context. No wasted words, front-loaded with key function.

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 tool with one optional param and no output schema, the description covers function, usage context, and availability completely.

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 single optional parameter 'motor' is fully explained: omit for all motors, specify for one. This adds meaning beyond the schema's minimal type info, compensating for 0% schema coverage.

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 clearly states the tool stops motion on one motor or all motors if omitted, using specific verbs (halt) and distinguishes from siblings like move or home.

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 explicitly says when to use the tool ('for stop, halt, cancel, or any sign something is wrong') and notes it is always available, providing clear context without needing to state exclusions.

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