delete_dns_zone

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description's 'ДЕСТРУКТИВНО' warning is consistent. The description adds valuable context beyond annotations: it specifies that the operation deletes all records and metadata, and that it requires pdns/edit rights. This is meaningful behavioral disclosure for a destructive tool.

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 two short sentences with no filler. The core action and destructive scope are front-loaded, followed by the permission requirement. Every word earns its place.

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 two-parameter tool with a confirm flag and full schema coverage, the description is nearly complete. It covers what is deleted, the destructive nature, and the required permission. It does not describe the response format, but there is no output schema and the operation is a simple delete, so this is a minor gap.

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%, so the schema already documents both parameters ('Имя зоны' and 'Must be true to run the operation'). The description adds no additional parameter-level detail beyond what the schema provides, so the baseline 3 is appropriate.

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), a specific resource ('DNS-зону по имени'), and the full scope of what is deleted ('вместе со всеми записями и метаданными'). It also names the internal operation (pdns/delete_zone), which distinguishes it from sibling tools like delete_dns_domain, delete_dns_record, and delete_dns_subdomain.

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 clearly indicates this is a destructive operation and requires the pdns/edit permission, which helps an agent decide whether it is authorized to call it. It does not explicitly name alternatives or state when not to use it, but the destructive warning and permission requirement provide clear context for when it is appropriate.

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