stop

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

With no annotations provided, the description carries the full burden of behavioral disclosure, and it delivers key traits: the operation is irreversible ('not resumable') and requires explicit confirmation ('Requires confirm: true'). This gives an agent a clear safety profile for the tool without needing additional context.

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 sentence that front-loads the core action ('Cancel the running print') followed by the key caveat and the parameter requirement. Every word earns its place, with no redundancy or 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 simple one-parameter tool, the description covers the essential elements: the action, irreversibility, and the confirmation requirement. It does not mention edge cases like errors when no print is running, but this is acceptable given the low complexity and absence of an output schema.

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 100%, so the schema already fully documents the confirm parameter. The description's 'Requires confirm: true' essentially restates the schema's requirement without adding new semantic detail, so it does not go beyond the baseline.

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 states the specific verb 'Cancel' with the resource 'the running print,' making the tool's function immediately clear. The parenthetical '(not resumable)' further distinguishes it from sibling tools like pause and resume.

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 'not resumable' implies this tool is for permanent cancellation, contrasting with pause/resume siblings, but it does not explicitly state when to use stop versus those alternatives. 'Requires confirm: true' is more of a parameter requirement than usage guidance. The usage context is implied rather than explicitly stated.

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