Get Transfer Setup

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, non-destructive), so the bar is lower. The description adds genuine value by disclosing the specific state it reports (PENDINGDNS hold, DNS zone presence, delegation, next step), which is the behavioral content an agent needs and is not present in any structured field.

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?

Two sentences, front-loaded with the core purpose before the usage hint. The colon-list is dense but every clause maps to a real reported field; slightly run-on but no filler.

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?

With no output schema, the description compensates by enumerating exactly what the tool returns. Combined with annotations that cover safety and the fully-documented single parameter, an agent has everything needed to invoke it correctly.

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 there is a single documented parameter, so the schema carries the semantics. The description references 'the domain' but adds no syntax or format detail beyond the schema's example, so baseline 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 states a specific verb (Report) and a precise resource/scope: a held inbound transfer, with an enumerated list of the state it surfaces (PENDINGDNS, DNS zone existence, record count, delegation, next step). This is clearly distinguishable from sibling tools like get_transfer_status or list_transfers by its 'held inbound transfer' and 'no-downtime' framing.

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?

It gives an explicit use case: 'Use this to resume a no-downtime transfer instead of tracking that state yourself.' That tells the agent when the tool is appropriate, though it does not name alternative tools or state when-not-to-use conditions.

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