set_dns_hosts

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

With no annotations provided, the description carries the full burden. It explicitly states the destructive behavior (deleting omitted records) and the side effect of switching DNS provider. This gives the agent full transparency beyond what annotations would provide.

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 extremely concise: two sentences plus a warning, front-loaded with the core purpose and a clear warning. Every word adds value without redundancy.

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 lack of output schema and three parameters, the description covers all necessary context: what the tool does, its destructive nature, the required workflow, and parameter hints. It is fully adequate for an agent to understand and use the tool 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 coverage is 100%, so baseline is 3. The description adds meaning by explaining that the 'records' parameter must be the COMPLETE set (omitted records are deleted) and that 'email_type' should be set to MX when including MX records. This context helps correct usage beyond the schema.

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 the action: 'Replace ALL DNS host records for a domain.' It uses a specific verb (Replace) and identifies the resource (DNS host records for a domain). This distinguishes it from sibling tools like get_dns_hosts or set_custom_nameservers.

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 explicit guidance: it warns that the call is destructive ('Namecheap deletes any record not included here') and instructs the user to first call get_dns_hosts, merge changes, then send everything. It also notes that it switches the domain to Namecheap DNS if needed, covering when this tool is appropriate.

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