Сервисы в VPC

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

The description describes a read-only list operation ('Возвращает список'), but the annotations specify readOnlyHint=false, which contradicts the read-only nature implied by the description. No additional behavioral context is provided, and the annotation conflict leaves the agent uncertain about potential side effects. This is an Annotation Contradiction.

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 directly states the function and enumerates the returned service types. No filler or redundant phrasing is present.

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 single-parameter list operation, the description covers the basic purpose and parameter. However, the contradiction between the read-only description and readOnlyHint=false creates significant ambiguity about the tool's behavior, making it incomplete for an agent to confidently invoke it without risking unintended effects.

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 description covers the only parameter (vpc_id) with 'ОБЯЗАТЕЛЬНОЕ ПОЛЕ - ID VPC' (REQUIRED FIELD - VPC ID), providing 100% coverage. The tool description adds no further meaning beyond restating that services are attached to the VPC. With full schema coverage, the baseline score 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 uses a specific verb 'Возвращает список' (returns a list) and explicitly names the resource type (services in VPC) with the service types enumerated (server / balancer / dbaas). This clearly distinguishes it from sibling tools like list_vpc_ports or list_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?

The intended usage is implied by the description: use when you need to list services attached to a VPC. However, there is no explicit guidance about when not to use it, nor any mention of alternative tools for similar purposes (e.g., list_vpc_ports). The usage context is present but not elaborated.

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