resume_print

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

The annotation destructiveHint=true already signals a potentially impactful operation. The description adds valuable context beyond that by stating 'Needs the user's explicit confirmation,' which tells the agent a confirmation step is required before execution. It does not detail what happens to the print state, but this is a meaningful addition.

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 short sentences, front-loaded with the action and followed by the critical prerequisite. No wasted words.

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 destructive tool with two parameters and no schema descriptions, the description is too sparse. It omits any explanation of the required 'host' parameter, the 'confirmation_code' parameter, and does not mention alternatives or post-resume behavior. While the destructive annotation covers safety, the definition remains incomplete for correct invocation.

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% for two parameters. The description only vaguely implies the confirmation_code parameter via 'explicit confirmation' and says nothing about the required 'host' parameter, its format, or how to obtain a confirmation code. It fails to compensate for the missing schema documentation.

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 a specific verb and resource: 'Resume a paused print.' This unambiguously distinguishes the tool from its siblings pause_print, start_print, and cancel_print without needing to name them.

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 'Resume a paused print' implies the tool is used when a print is paused, and the confirmation requirement is a useful prerequisite. However, it does not explicitly say when to choose this over pause_print or cancel_print, nor does it describe handling of non-paused prints.

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