domain_transfer

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

With no annotations, the description carries the full burden. It mentions the tool returns an auth code but does not disclose potential side effects (e.g., domain status changes, code expiration) or error conditions.

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 (two sentences), with the purpose stated upfront. No unnecessary information, making it easy to parse.

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 retrieval tool with one parameter and an output schema, the description is minimally adequate but lacks details on return format and prerequisites. Given the sibling tools, it could be more 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 single parameter 'domain' has no additional meaning added beyond its schema title. Schema description coverage is 0%, and the description fails to specify expected format (e.g., full domain name with TLD).

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 it retrieves the EPP authorization code for domain transfer. The verb 'Get' and resource 'EPP authorization code' are specific, and the tool is easily distinguished from sibling tools like domain_buy, domain_check, and domain_dns_update.

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 implies the tool is used to obtain an auth code for transferring a domain, but provides no explicit guidance on when to use it vs alternatives, or prerequisites like domain unlock or transfer restrictions.

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