Получение списка VPC

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

The description describes a read-only operation ('gets list'), but annotations have readOnlyHint=false, suggesting the tool may not be read-only. This is a contradiction and no additional behavioral context is provided.

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 core function with no wasted words.

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 simple and adequate for a zero-parameter listing tool, but it omits the return format and does not clarify the read-only contradiction stemming from annotations. Since annotations are contradictory, completeness suffers.

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 tool has zero parameters and empty schema, so baseline is 4. The description adds nothing about parameters, but none exist.

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 a specific action: 'Получает список всех виртуальных частных сетей (VPC) пользователя' (gets list of all user's VPCs). It distinguishes from sibling tools like get_vpc (singular) and list_vpc_services by explicitly indicating all VPCs.

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?

Usage is implied by the tool name and description: it lists all VPCs. However, there is no explicit guidance on when to use it vs alternatives (e.g., get_vpc for a single VPC) or any exclusions.

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