delete_dns_subdomain

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 'ДЕСТРУКТИВНО' is reinforcing rather than new. However, the required permission (pdns/edit) is genuinely additional behavioral context not present in the structured fields, and it tells the agent what authorization is needed before calling.

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?

Three short sentences, front-loaded with the action, with zero wasted prose. The destructive warning slightly duplicates the annotation, but the sizing is otherwise tight.

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 tool with full schema coverage, annotations covering the safety profile, and no output schema, the description supplies what the agent still needs: the target scope and the required permission. Only the absence of sibling routing keeps it from a 5.

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 coverage is 100% with descriptions for id, server_id, and confirm (including 'Must be true to run the operation.'). The description adds no parameter-level meaning beyond the schema, so 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 (Cyrillic, mojibake-encoded) description states a specific verb+resource: delete a subdomain from the subdomain table, and even names the underlying API endpoint (pdns/delete_subdomain). It is distinguishable from delete_dns_domain by scoping to 'subdomains', though it does not explicitly contrast with that sibling.

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 states the prerequisite permission (pdns/edit), which is useful context for deciding whether the call will succeed, but it gives no explicit when-to-use/when-not guidance or routing to alternatives such as edit_dns_subdomain.

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