dns_zone_delete

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but 'Delete a DNS zone' only restates the action already implied by the tool name. It does not disclose that deletion is likely irreversible, whether associated DNS records are cascadingly removed, what permissions are required, or error behavior for non-existent zones.

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?

A single clean sentence with zero filler and the action front-loaded. It is appropriately brief, though it errs toward under-specification rather than being merely concise.

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 mutation tool with no annotations and no output schema, this description is the bare minimum. It omits critical operational context such as side effects on records, irreversibility, success/error return behavior, and how it fits into the broader DNS zone CRUD workflow (dns_zone_list/get/add/update/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 description coverage is 100%, as zone_id is documented as 'Zone ID to delete' in the schema itself. The description adds no parameter meaning beyond the schema, so the baseline of 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'), making the core purpose unambiguous. However, it does not differentiate itself from the sibling set (dns_zone_add, dns_zone_update, dns_zone_get, dns_zone_list), relying entirely on the verb to carry that distinction.

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?

No guidance is provided on when to use this tool versus siblings. It does not mention prerequisites (e.g., zone must exist), conditions that would make deletion inappropriate, or alternatives like dns_zone_update for modifying instead of removing.

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