cancel_handoff

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

Annotations already declare destructiveHint=true and non-idempotent behavior, so the safety profile is partly covered. The description adds the important status constraint ('pending or approved'), but does not disclose consequences such as whether cancellation is reversible, notifies contacts, or requires special permissions.

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 front-loaded sentence with no wasted wording. Its brevity is appropriate, though the resource naming issue keeps it from being fully precise.

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 mutation tool with no output schema, the definition is too thin. It omits expected result behavior, permissions, side effects, and what 'cancel' means for an approved handoff, leaving the agent with only a status restriction.

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%, and the single required handoff_id parameter is not explained in the description. The description's use of 'preview' may even confuse what the handoff_id refers to, so it does not compensate for the schema gap.

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 gives a specific verb ('Cancel') and eligibility states ('pending or approved'), but calls the resource a 'preview' even though the tool name is cancel_handoff. That mismatch makes the target resource less clear and does not distinguish it well from siblings like prepare_handoff.

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 says cancellation applies to pending or approved previews, but does not explain when to use this tool instead of prepare_handoff or other handoff-related siblings. There are no explicit exclusions or prerequisites.

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