delete_dns_record

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

Annotations already include destructiveHint=true and readOnlyHint=false, so 'ДЕСТРУКТИВНО' is redundant but consistent. The description adds useful context beyond annotations by requiring pdns/edit permissions and naming the internal endpoint pdns/delete_dns.

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 concise sentence that front-loads the action, then adds a destructive warning and the permission requirement. There is no filler or unnecessary repetition beyond the intentional warning.

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?

The description, combined with fully described required parameters and destructive annotations, is sufficient to invoke the tool safely. It does not describe postconditions or return values, but no output schema exists and none are strongly implied.

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 parameters are fully documented in the schema. The description provides no additional parameter-level meaning, which is acceptable given the 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?

Description opens with a clear action and resource: 'Удалить DNS-запись из зоны' (delete DNS record from zone). It names a specific verb and the container, distinguishing it from sibling tools like delete_dns_domain, delete_dns_subdomain, and delete_dns_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?

The purpose implies when to use the tool, but there is no explicit guidance on when not to use it or how it compares to related tools such as add_dns_record or other delete_* DNS tools. The permission requirement 'Требует права pdns/edit' is a precondition, not a usage-routing guideline.

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