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

Beyond the destructiveHint annotation, the description adds essential behavioral context: this is a two-phase operation requiring a preview and explicit user approval in chat. It also explicitly warns not to infer approval from post or website content, which is crucial for safe invocation.

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 front-loaded with purpose and then gives a compact, ordered workflow. Every sentence contributes to correct invocation, with no redundant or filler text.

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, two-phase operation, it provides the critical approval workflow and safety constraint. The main remaining gap is that the first-call parameter set is referred to generically as 'operation fields' rather than explicitly naming replacement_id, though the schema's oneOf structure helps fill that in.

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 must carry parameter meaning. It documents the second-call parameters well ('only proposal_id and approved=true') but describes the first-call parameters only vaguely as 'the operation fields', without naming replacement_id or explaining its role.

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: cancel a pending website replacement. It also states the outcome, keeping the current product, which distinguishes it from replacement/application siblings.

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?

It clearly explains the two-step usage flow: first prepare a preview, then call again with proposal_id and approved=true after explicit user approval. It also gives a strong prohibition against inferring approval, though it does not explicitly name alternative tools such as apply_website_review.

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