Stop

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

Annotations only declare readOnlyHint=false and idempotentHint=true, so the description carries the burden of saying what the mutation touches, and it does: movement is cancelled, autopilot is switched off, and the simulation is paused. It does not say whether the paused state can be resumed or how autopilot gets re-enabled, which is the main remaining behavioral gap.

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?

One sentence, front-loaded with the emergency framing followed by the concrete effects, with no filler.

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 zero-parameter mutation with no output schema, the description covers the full scope of side effects. What is missing is lifecycle context: whether the simulation stays paused, and which sibling (open_simulator, set_autopilot, stop_program) resumes the stopped work.

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 tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a no-param tool applies.

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?

A specific verb (stop) with an enumerated effect list: cancel movement, turn autopilot off, pause the simulation. That tells an agent exactly what is affected. It does not distinguish itself from siblings such as stop_program or reset_world, so the agent can't tell from this text whether 'stop' is a superset of, or disjoint from, those tools.

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 word 'Emergency' implies a usage context, but nothing states when to prefer this over stop_program or reset_world, nor whether it should be followed by any recovery step. Usage is implied rather than specified.

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