transferUpdateChangeEPPCode

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states that the tool mutates the EPP code, but does not mention side effects, preconditions beyond 'pending transfer', reversibility, response format, or error behavior. This is a notable transparency gap for a write operation.

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 a single, direct sentence with no filler or redundancy. It front-loads the action and resource, and the API reference link provides optional additional context without bloating the description.

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 complete schema descriptions, the description provides the essential resource and the 'pending transfer' precondition. However, because there is no output schema and no annotations, some missing behavioral context (such as expected response or consequences of changing the code) leaves the description only adequately complete rather than thorough.

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 input schema already documents both parameters ('domain' and 'auth') with useful descriptions, giving 100% schema description coverage. The tool description adds no additional meaning beyond the schema, 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 uses a specific verb ('Set or change') and a clear resource ('EPP/auth code on a pending transfer'). It distinguishes this from sibling transfer operations like resending admin email or resubmitting to registry, even though it doesn't name them.

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 phrase 'on a pending transfer' implies when the tool should be used, but there is no explicit guidance about when not to use it or which sibling operation to choose instead. The context is clear enough for a simple case, but not fully spelled out.

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