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

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

The description explicitly states 'Операция необратима' (the operation is irreversible), which directly contradicts the annotation 'destructiveHint': false. This is a serious inconsistency that misleads the agent about the tool's side effects, warranting a score of 1.

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 concise at two sentences, but the second sentence ('отвязывает домен от аккаунта') largely repeats the action stated in the first sentence ('Удаляет домен с аккаунта'), adding minor redundancy. Still, it is compact and front-loaded.

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 one parameter and no output schema, the description covers the action and irreversibility. However, the contradiction with the destructiveHint annotation leaves ambiguity about the actual destructive nature, and it does not mention any side effects or prerequisites. It is adequately rich but undermined by the inconsistency.

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?

The input schema fully documents the single 'fqdn' parameter (schema coverage 100%), including a description that it is required and the full domain name for deletion. The description's mention of 'FQDN' reinforces this but adds no new semantic information beyond the schema. 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 clearly states the tool's function: 'Удаляет домен с аккаунта по FQDN' (Deletes a domain from the account by FQDN). It uses a specific verb and resource, distinctly differentiating it from sibling tools like add_domain, update_domain, and get_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 intended use case is implied by the verb 'deletes' and the resource 'domain', but the description provides no explicit guidance on when to use this tool versus alternatives, nor does it mention any exclusions. It lacks direct recommendations or cautionary notes beyond the operation itself.

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