Удаление VPC

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

The description says 'Удаляет' (deletes), which is a destructive action, yet the annotation destructiveHint=false. This is a direct contradiction. The description adds no other behavioral context such as prerequisites or consequences.

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 sentence that immediately conveys the action and key parameter. It is concise and front-loaded with the verb.

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 is minimal and insufficient for a delete operation. It lacks any mention of return values, error conditions, or preconditions, and the contradiction with annotations leaves the agent confused about whether the operation is destructive. Given no output schema, more context is needed.

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 schema fully covers the only parameter vpc_id with a required field description. The description merely restates 'by its ID,' adding no new semantic information beyond the schema, so it meets the baseline of 3.

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 states 'Удаляет виртуальную приватную сеть (VPC) по её ID' (Deletes a VPC by its ID). This is a specific verb+resource, clearly distinguishing it from other VPC operations like create_vpc, update_vpc, get_vpc.

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 provides no explicit guidance on when to use this tool versus alternatives. It only states the action and parameter, leaving usage context implied from the tool name.

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