Cancel pending IRTP verification

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

The annotations already convey the core behavioral profile: readOnlyHint=false, destructiveHint=true, and idempotentHint=true. The description adds useful context about the 5-day expiry and the stuck-WHOIS-change scenario, but it does not disclose side effects, reversibility, or the post-cancellation state, which would add further value.

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 concise and well-structured: the first sentence states the action directly, and the second provides a concrete use case with no filler or redundant wording.

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 action, the description covers the purpose, trigger scenario, and rationale well. It does not describe the response format or error cases—especially relevant since there is no output schema—but the low complexity and clear annotations make this nearly complete.

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?

The schema already documents the only parameter (domain) with 100% coverage. The description does not add any parameter-level detail beyond what the schema provides, so the 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 opens with a direct verb-resource statement: 'Cancel a pending IRTP verification.' It further clarifies the scope by explaining it applies to a WHOIS change stuck waiting on registrant confirmation, which distinguishes it from related read-only tools like domains_getPendingIRTPVerificationV1.

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 it: to back out of a WHOIS change stuck on registrant confirmation, such as when the confirmation email cannot be received, and to avoid waiting out the 5-day expiry. It does not explicitly name alternatives or list when not to use it, so it stops short of a 5.

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