stop_motors

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

Annotations already convey that the operation mutates state, is idempotent, and is not destructive, which lowers the burden on the description. The description adds the 'together' behavior, but it does not disclose what happens while stopping, whether the call blocks, or how the brake parameter affects motor behavior beyond the schema default.

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 extremely concise: a single eight-word sentence with no filler. The action, object, and scope are front-loaded.

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, the description is minimally viable, but it omits important selection context versus emergency_stop and stop_motor. An agent could still invoke it correctly using the schema, but would benefit from knowing when the brake flag should be set or whether this is the right batch-stop tool for a scenario.

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 needed to clarify parameters, but it does not mention ports or brake by name. It only implies the ports array length through 'one to three', leaving brake semantics entirely to the schema.

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 uses a clear verb ('Stop') with a precise resource ('motors') and a scope ('one to three ... together'). It distinguishes this batch tool from the singular sibling stop_motor by emphasizing togetherness and plural motors.

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 phrase 'one to three motors together' implies the intended use case: stopping multiple motors in one call. However, it does not explicitly say when to use this tool instead of related siblings like emergency_stop, wait_motors, or stop_motor, or when the brake option should be used.

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