delete_dns_domain

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description still adds genuine value beyond them: the cascade deletion of all subdomains and the required pdns/edit privilege, both of which the annotations do not convey.

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 compact line: what is deleted, how destructive it is, and what permission it needs, in that order. No filler and nothing buried.

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 3-parameter destructive tool with no output schema, the description covers scope, cascade effect, and the auth requirement, which is what an agent needs before calling. The main defect is presentation rather than substance: the text is mojibake-corrupted Cyrillic, which reduces readability for downstream consumers.

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% (server_id, domain_id, and the confirm flag are all documented in-schema), so the baseline is 3. The description adds the 'by ID' framing and the note that domain_id comes from list_dns_domains, but no syntax or format detail beyond what the schema already 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 states a concrete verb and resource (delete domain by ID) and spells out the exact blast radius: the DNS zone, the domain itself, and all its subdomains. That scope statement lets an agent distinguish it from siblings like delete_dns_subdomain or delete_dns_zone without opening any schema.

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?

It names a prerequisite (requires pdns/edit permission) and the underlying API path, but never says when to choose this over the adjacent delete_dns_zone / delete_dns_subdomain tools, nor any when-not condition. Usage is implied by the cascade scope rather than explicitly stated.

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