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

Annotations already mark destructiveHint: true, so the description's 'paid transfer' is consistent. It adds valuable context: the code is used once and never stored (privacy/consumption), and transfers take days (timeframe). These go beyond the annotation and help the agent understand side effects and follow-up needs. No contradiction.

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?

Three concise sentences, each adding value: the action, the code's fate, and the tracking guidance. No filler. The most critical info (what it does) is front-loaded, and the alternative tool is named at the end. Efficient and well-structured.

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?

The description covers the core action, prerequisite (auth code), side effects, and next step (track). However, it omits the likely prerequisite of creating a transfer checkout (sibling formation_create_domain_transfer_checkout) and does not mention the need for a companyId (a required parameter). Given the existence of an output schema, return format need not be described, but the flow before and after is partially incomplete.

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 coverage is only 33% (only companyId has a generic wrapper description). The description explains that the authCode is the EPP code the user obtained from the current provider, giving it semantic meaning. It implies 'domain' via 'transfer', but doesn't explicitly define it. companyId remains unexplained, and with a nested object structure, the description does not compensate fully for the low schema coverage.

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 clearly states the action: 'Begins the paid transfer at the registrar' using the EPP/auth code. It specifies the verb (begins), resource (domain transfer), and the method (EPP code). It distinguishes itself from tracking tools by explicitly naming the transfer-status tool for follow-up, and from checkout tools (not named but implied) by focusing on the actual transfer initiation. The purpose is unambiguous.

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 clear context on when to use: when the user has an EPP/auth code from their current provider. It also directs the user to the transfer-status tool for tracking, which is an alternative for post-transfer monitoring. However, it does not mention prerequisites like creating a transfer checkout first (implied by sibling formation_create_domain_transfer_checkout), nor explicitly state when not to use (e.g., if domain is already transferred).

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