bunny_delete_dns_zone

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

Annotations already declare destructiveHint=true and idempotentHint=true. The description adds crucial context beyond that: records are deleted, DNS resolution stops if nameservers are active. This fully discloses the behavioral impact without contradicting annotations.

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 with zero waste. The purpose is stated first, followed by the critical consequence. Every sentence earns its place and is immediately scannable.

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 single-parameter destructive tool, the description, schema, and annotations together provide everything an agent needs: what it does, consequences, and the required parameter. No output schema exists, so nothing is missing.

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 100% with a clear 'DNS Zone ID' description. The tool description does not add additional parameter meaning, but the schema already documents it fully, so baseline 3 applies.

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 states a specific verb (delete) and resource (DNS zone) with scope (all its records). It clearly distinguishes from sibling tools like bunny_create_dns_zone, bunny_list_dns_zones, and bunny_update_dns_zone by its irreversible nature.

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 provides clear context on consequences (irreversible, stops DNS resolution) and implies it is for permanent deletion. It does not explicitly name alternatives but the warning makes it clear when not to use it (if the zone is needed).

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