delete dns domain

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

Annotations already signal destructiveHint=true, and the description adds meaningful behavioral nuance by warning that all records in the zone are deleted, not just the zone object itself. It also names the underlying verified command v-delete-dns-domain, adding execution context beyond the 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?

The description is concise and front-loaded with the core purpose. The second sentence about the verified command is useful but somewhat redundant with the tool name, so it is not maximally economical.

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 simple destructive tool, the description plus annotations and schema convey the core operation, required confirmation, and destructive scope. However, it lacks guidance on when to choose this instead of delete_dns_record and does not clarify domain format or user ownership, so it is minimally adequate but not complete.

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 only 33%, and the description partially compensates by clarifying that 'domain' refers to a DNS zone whose records are removed. However, it does not explain the 'user' parameter or the expected domain format, leaving a meaningful gap for two of three parameters.

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 and resource: 'Delete a DNS zone and all records.' This clearly differentiates it from the sibling delete_dns_record, which operates on a single record rather than the entire 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?

There is no explicit guidance on when to use this tool versus alternatives such as delete_dns_record. The description only implies zone-level deletion; it never states conditions, exclusions, or which sibling to use for record-only deletions.

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