Delete DNS zone

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

Despite only having destructiveHint=true, the description adds important context: the deletion is permanent and irreversible, and confirm=true is required. This goes beyond the annotation by clarifying the confirmation requirement and the scope of deletion.

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 composed of three short, purposeful sentences that front-load the core purpose and then add critical caveats. There is no filler or redundant exposition.

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 covers the essential behavioral aspects for a delete operation: what is deleted, irreversibility, and the confirmation requirement. While there is no mention of return value or asynchronous behavior, the simple schema and destructive annotation make the description adequate for agent selection.

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 provides complete descriptions for both parameters, including the requirement for confirm and the need to ask the user. The tool description's mention of 'Requires confirm=true' adds no new information beyond what the schema provides.

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 uses the specific verb 'delete' and clearly identifies the resource as a DNS zone, specifying that all records are removed. This distinguishes it from sibling tools like delete_rrset and update_zone.

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 establishes that this tool is for entire zone deletion, including all records, implying it should not be used for individual record operations. However, it does not explicitly mention alternatives or provide exclusionary guidance, so it falls short of a 5.

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