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

Beyond the annotations, the description adds valuable behavioral context: the operation is destructive and irreversible once executed, requires authentication, returns an actionId, and is only a staging step rather than the final execution. This directly helps the agent understand the two-phase nature of the cancellation and what to do with the result.

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 compact and front-loaded: purpose first, then the safety warning, then the workflow. Every sentence contributes essential information, and the warning about destructiveness is prominent before the user proceeds.

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 two-parameter tool with rich annotations, the description covers all critical aspects: what it does, what it returns, the required follow-up action, the destructive nature, and authentication. Nothing an agent needs to call it correctly or handle its result is missing.

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 both parameters. The description does not add parameter-specific meaning, but it also doesn't need to; the schema carries the burden. A baseline score of 3 is appropriate.

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 uses a specific verb ('Stage cancellation') and resource ('pending domain transfer'), and clearly distinguishes this tool from the actual execution step by naming executeConfirmedAction as the follow-up. It also implies the domain must currently be pending, distinguishing it from transfer initiation 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 description explicitly states when to use this tool (for a pending domain transfer) and outlines the exact workflow: after calling it, present the returned summary and call executeConfirmedAction with the actionId if the user approves. This gives the agent clear routing and next-step guidance without ambiguity.

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