dnsSet

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description's job is to add beyond that — and it does: it scopes the destruction to named record sets while preserving others, and discloses the optimistic-concurrency precondition ('requires the current DNS revision'). It does not say what happens on a stale revision or whether changes are recoverable.

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, no filler, with the preservation guarantee and the revision precondition front-loaded where an agent will see them before invoking.

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?

For a destructive, open-world mutation with no output schema and fully undocumented parameters, the description covers the key precondition but omits failure behavior on a stale revision, return shape, and record-level constraints. Adequate but with clear gaps against the tool's complexity.

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 0% with 3 required parameters, so the description must compensate. It clarifies the meaning of 'revision' (the current DNS revision, a concurrency token) and implies 'records' are named record sets, but says nothing about 'domain' or the record object's required fields, TTL bounds, or the 50-item cap.

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 (replace/set) and resource (DNS record sets) plus the exact scope: 'only named DNS record sets, preserving other names and types.' This distinguishes it from the read-oriented dnsGet sibling by action, though it never names the sibling explicitly.

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 'only named ... preserving other' phrasing implies when the tool is appropriate (partial updates versus a full zone replacement), but it gives no explicit when-to-use/when-not guidance or names an alternative in the sibling list. Usage is inferable rather than stated.

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