Удаление поддомена

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

The description indicates a destructive deletion operation, but the annotation destructiveHint is false, directly contradicting the described behavior. This inconsistency misleads the agent about the tool's effects.

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 efficiently states the action, resource, and identifying context without unnecessary details. Every word contributes to understanding.

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 delete tool with two fully described parameters and no output schema, the description adequately covers the operation's scope and required inputs. The annotation contradiction is a flaw but doesn't diminish the description's inherent completeness.

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 both parameters are fully documented in the schema. The description's mention of 'by FQDN' and 'from main domain' adds no additional semantic meaning beyond what the schema already provides.

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 clearly states the tool deletes a subdomain by its FQDN from a specified main domain. It uses a specific verb (Удаляет) and resource (поддомен), distinguishing it from sibling tools like add_subdomain and delete_domain.

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 usage for deleting subdomains but provides no explicit guidance on when to use this tool versus alternatives, nor does it mention exclusions or prerequisites. The context is clear but not differentiated.

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