delete_dns_domain

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

The description explicitly flags the operation as 'ДЕСТРУКТИВНО' (destructive) and details exactly what is destroyed: DNS zone, the domain, and all subdomains. It also adds the authorization requirement 'pdns/edit' and the backend endpoint, going beyond the destructiveHint annotation. No contradiction with 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 a single, front-loaded sentence that covers action and scope, followed by two short fragments for the destructive warning and permission. No filler or redundant explanation.

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 three-parameter delete operation with destructive annotations and full schema descriptions, the description provides the necessary behavioral context: what gets deleted, required rights, and the destructive nature. The lack of an output schema is acceptable for a delete tool, and the confirm parameter is documented in the schema. The only minor gap is that it doesn't explicitly mention DNS records, but 'DNS zone' implies them.

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?

All three parameters are already fully described in the input schema (100% coverage), including confirm semantics, domain_id provenance, and server_id. The description only adds a generic 'by ID' phrase and does not provide additional parameter meaning, so it stays at the baseline for high schema coverage.

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 action 'delete domain by ID' and enumerates the full destructive scope: DNS zone, the domain itself, and all subdomains. This clearly distinguishes it from siblings like delete_dns_subdomain or delete_dns_zone. The backend operation (pdns/delete_domain) adds a concrete reference.

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 implies when to use it by specifying what it deletes (the entire domain plus zone and subdomains) and states the required permission 'pdns/edit'. It does not explicitly name alternatives (e.g., delete_dns_subdomain for single subdomains) or state when not to use it, so it is clear context but lacks explicit exclusions.

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