dns_delete_zone

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

Annotations already declare destructiveHint=true, but the description adds real value beyond that by disclosing blast radius — deleting the zone also destroys all its records — and the required OAuth scope. It stops short of stating irreversibility/no-undo or that the confirm parameter is a safety gate, which would complete the picture for a destructive operation.

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, zero filler, with the action and its consequence front-loaded and the auth constraint trailing. Nothing could be removed without losing information.

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 2-parameter destructive tool with no output schema, the description covers what is deleted, the blast radius, and the required scope, while the schema handles the confirm mechanics. It is only slightly short of complete in not flagging that the deletion is irreversible.

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 100% and both parameters are documented, including that confirm is a typed repeat of the domain, so the baseline is 3. The description adds nothing about either parameter — notably it never mentions that a confirmation string is required, which is the tool's key safety mechanism.

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 a zone") with its scope ("and all its records"), which implicitly separates it from dns_delete_record in the sibling list. It does not explicitly name that sibling or dns_get_zone as the read counterpart, so differentiation is inferable rather than stated.

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 on when to use this versus alternatives, no note that the zone must be empty-checked or that records are deleted implicitly rather than via dns_delete_record. "Scope dns:write" signals an auth prerequisite but is not usage guidance.

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