Add / update / delete DNS records (safe)

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

Annotations already mark destructiveHint and non-readOnly, but the description goes far beyond: it explains the read-merge-write workflow, untouched-record preservation, the allowEmptyZone safety switch, and the GoDaddy non-atomic delete-then-create caveat (if create fails the record is ABSENT, not stale). This is critical, actionable behavior not derivable from annotations alone, and it contradicts nothing.

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 long but dense. It front-loads the most important rule ('WITHOUT wiping the zone'), then systematically covers operation grammar, safety, return value, and provider-specific behavior. Every sentence carries operational weight; there is no filler. Slight length is justified by complexity.

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 nested operations array, multiple providers, and mutation risk, the description covers all essential context: how operations are matched, the allowEmptyZone guard, the diff return, and the non-atomic provider caveat. The output schema exists, so not detailing return fields is fine. This is a fully self-sufficient description for safe invocation.

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%, but the description adds meaning beyond field descriptions: update matches name+type optionally matchAddress and only touches provided fields; delete similarly; address is required for add, optional for update; allowEmptyZone is a safety switch. This is exactly the semantic depth needed for correct operation construction.

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 opens with 'Change DNS records WITHOUT wiping the zone', a specific verb-resource pair that instantly distinguishes it from replace_all_dns_records. The scope (granular add/update/delete vs. wholesale replacement) is explicit, making the tool's purpose unambiguous among sibling tools.

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 explicitly positions itself as 'the tool you almost always want' and contrasts with the destructive alternative by saying 'WITHOUT wiping the zone'. It also gives concrete guidance for using the provider parameter (domain not existing yet, or domain at two providers). However, it doesn't name the alternative tool directly, only implies it.

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