delete_dns_zone

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

Annotations already mark destructiveHint=true, so 'ДЕСТРУКТИВНО' partly repeats that signal. The description adds value by specifying that all records and metadata are removed and that the 'pdns/edit' permission is required, which go 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?

Two short sentences with no filler: the action and destructive consequence are front-loaded, followed by the permission requirement. The compact technical reference '(pdns/delete_zone)' adds useful backend clarity without bloat.

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 two-parameter delete operation with destructiveHint and full schema coverage, the description covers what is deleted, the required permission, and the destructive nature. No output schema exists, but that is acceptable for this delete operation; nothing essential is missing.

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%, with clear descriptions for zone ('Имя зоны') and confirm ('Нужно true, чтобы выполнить операцию'). The description's 'по имени' aligns with zone but adds no semantic detail beyond the schema, so the baseline of 3 applies.

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 begins with a specific verb and resource: 'Удалить DNS-зону' (delete DNS zone), and further specifies the scope: 'вместе со всеми записями и метаданными' (with all records and metadata). This clearly distinguishes it from the sibling record/domain/subdomain deletion tools.

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 provides useful context that this is a destructive zone-level deletion and that it requires 'права pdns/edit'. However, it does not explicitly state when to prefer this over related deletions such as delete_dns_record or delete_dns_domain, so usage context is implied rather than spelled out.

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