Set records of an RRSet

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

The description goes beyond the destructiveHint annotation by explicitly stating 'Existing records not listed are removed.' This discloses the exact destructive behavior, informing the agent about the consequences of using this tool.

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 two sentences, front-loaded with the core action, and contains no filler. Every word contributes to understanding the tool's purpose and usage.

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?

The description is largely complete for a mutation tool with destructiveHint, covering the replacement semantics and the alternative tool. However, it does not specify whether the RRSet must already exist or how TTL is handled, which are minor gaps.

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?

The description clarifies that the 'records' parameter represents the complete replacement set, not just additions. This adds meaning beyond the schema's per-field descriptions, which only describe individual record values.

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 tool's action: 'Replace ALL records of an RRSet with the given records.' It uses a specific verb (Replace) and resource (RRSet), and distinguishes itself from add_records by emphasizing the replacement aspect.

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 provides both when-to-use ('Replace ALL records') and when-not-to-use context by stating 'Use add_records to append instead.' This gives a clear alternative and prevents misuse.

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