delete_rrset

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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is covered. The description adds real value by disclosing cascade scope (all records under the RRSet are removed) and the async return type ("Returns an Action"), which is important since no output schema exists, but it says nothing about permissions or recovery.

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 short sentences, both front-loaded and earning their place: the destructive scope first, the return contract second. There is no padding, though one clause on the Action's asynchronous nature would add clarity without bloat.

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 three-required-parameter destructive operation with no output schema, the definition covers the essentials: what is destroyed, at what granularity, and what comes back. What remains missing — permission requirements and whether the zone must retain NS/SOA records — is secondary but nontrivial for an irreversible delete.

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 67%, with name and zone documented and type constrained by an enum, so the schema carries most of the burden. The description contributes nothing about parameter meaning — notably it never clarifies that name is relative to the zone or how type interacts with the RRSet identity, so baseline 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?

States a specific verb and resource ("Delete an RRSet") and adds scope ("and all its records"), which distinguishes it from record-level siblings like remove_rrset_records. It does not name any sibling explicitly, so an agent must infer the boundary.

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?

There is no explicit when-to-use guidance: nothing says to prefer remove_rrset_records or set_rrset_records when only some records should go. The phrase "all its records" hints at the distinction but leaves it to inference, and no prerequisites or warnings are given.

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