Prepare Transfer

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

Annotations already declare idempotentHint=true, destructiveHint=false and openWorldHint=true, so the mutation-safety profile is covered. The description adds genuine context beyond that: the return value (Porkbun nameservers) and the rationale that the zone is created deliberately rather than as a write side effect, though it does not state what happens if the zone already exists or what auth is required.

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?

Four sentences, each earning its place, with the core purpose front-loaded ahead of the sequence context, the return value, and the rationale. No repetition of the title or restated annotation hints.

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?

Despite having no output schema, the description discloses the return value (nameservers) and anchors the call in its multi-step workflow, so an agent has everything needed to invoke it correctly in context.

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?

With a single parameter at 100% schema description coverage, the schema already documents 'Domain with a held inbound transfer.' The description reinforces the held-transfer precondition but adds no format or syntax detail beyond what the schema provides, so the baseline of 3 applies.

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?

States a specific verb and resource: create the Porkbun DNS zone for a domain with a held inbound transfer. It distinguishes itself from siblings by naming itself as step 2 of a defined sequence and explaining it is not the same as the first record write that would otherwise create the zone implicitly.

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?

Explicitly places the tool as 'Step 2 of the no-downtime sequence', naming the upstream sibling (transfer_domain with hold_for_dns_setup), itself, and the downstream calls (import_dns_records, start_transfer). The condition selecting this tool versus its siblings is left to no inference.

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