Cancel outgoing domain move

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

Annotations already signal readOnlyHint=false, idempotentHint=true, and destructiveHint=true. The description adds value by explaining the cancel condition and clarifying that the domain stays in the account, which mitigates the destructiveHint by showing the domain itself is not lost.

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 well structured: direct action first, then the key precondition, a clarifying consequence, and a final statement of intent. No sentence is wasted.

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 mutation with annotations and no output schema, the description covers what the tool does, when it can be used, and the expected effect on the domain. Nothing essential for correct invocation 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%, and the only parameter is already documented as 'Domain name.' The description adds no new parameter-level detail, so the schema carries the burden as expected.

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 and resource: 'Cancel an outgoing move for a specified domain,' and reinforces intent with 'withdraw a move you no longer want to complete.' This clearly distinguishes the tool from related domain move operations like start, accept, or reject.

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 provides an explicit precondition: the move can only be cancelled while the receiving account has not accepted it yet. It also states when to use it, but does not explicitly name alternative tools or situations where cancellation is no longer possible.

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