update_nameservers

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

Annotations already mark destructiveHint=true and idempotentHint=true. The description adds value by explaining the full replacement semantics, the consequence of disabling free DNS hosting, and a plain-language idempotency statement that reinforces the annotation without 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 serving a purpose: stating the action, clarifying the replacement nature with constraints, and noting idempotency. No redundant or missing information.

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?

Given the tool's simplicity (2 required params, no output schema), the description covers all needed behavioral and usage aspects. The side effect of disabling free DNS hosting is a valuable addition that ensures complete understanding.

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 100% with both parameters described. The description adds semantic value for nameservers by clarifying it is a full replacement and explaining the 2-13 entry requirement beyond the schema's range constraints. Domain parameter adds no extra semantics, but overall the description enhances understanding.

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 specifies the action 'Replace the nameservers for a domain' with a clear verb and resource. It distinguishes from read-only siblings like get_nameservers by emphasizing replacement, and explicitly states it is not an append.

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 usage context: full replacement (not append), TLD constraints (2-13 entries), and side effect (disabling free DNS hosting). It does not explicitly compare to sibling tools or state when not to use, but overall guidance is clear.

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