Получение VPC

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

The description discloses that the operation returns information, which is a read behavior, but it provides no extra context such as error handling, authentication requirements, or what 'detailed information' includes. Annotations do not add useful safety context (readOnlyHint is false, which is ambiguous for a get operation).

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 is front-loaded and directly states the action. No unnecessary words or repetition.

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 read tool, the description is adequate but vague about the exact details returned. With no output schema, the agent cannot know what fields to expect, and the description does not enumerate them or mention potential error cases, leaving some uncertainty.

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 coverage is 100%, with vpc_id clearly documented as required. The description adds minimal meaning by using 'по её ID' (by its ID), but does not elaborate on format, examples, or additional constraints beyond the schema.

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 returns detailed information about a VPC by its ID, using the specific verb 'Возвращает' and naming the resource. It distinguishes itself from the sibling get_vpcs (list all) by specifying a single VPC lookup.

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 when you have a VPC ID and need its details, which is clear context. However, it does not explicitly mention alternatives like get_vpcs for listing all VPCs or state when not to use this tool, though the purpose makes it obvious.

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