Delete RRSet

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

The description enhances the destructiveHint annotation by explicitly stating the action is irreversible and that confirm=true is required. It also discloses the full scope of destruction (all records in the RRSet), providing critical behavioral context beyond the annotation alone.

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, using three short sentences to convey action, consequence, and safety requirement. Every word earns its place, with no redundancy or filler.

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 tool, the description sufficiently covers the action, irreversibility, scale (all records), and the confirmation flag. There is no output schema, but for a delete operation this is not a significant gap. It could mention potential errors (e.g., RRSet not found), but the essentials are covered.

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 input schema already describes all four parameters with 100% coverage, including the confirm parameter's purpose. The description adds no additional semantic details about parameters beyond what the schema provides, so the baseline score of 3 is appropriate.

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 performs a permanent deletion of an RRSet and all its records, with an explicit verb and resource. It distinguishes itself from sibling tools like update_rrset or remove_records by emphasizing irreversibility and cascading deletion.

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 implies when to use the tool (to delete an RRSet), but it does not explicitly contrast it with alternatives such as remove_records or update_rrset. There is no when-not-to-use guidance, so it falls short of a clear usage guideline.

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