Список портов VPC

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

The description states the tool 'Возвращает' (returns) a list, implying a read-only operation. However, the annotation readOnlyHint is set to false, indicating the tool may not be read-only. This directly contradicts the description's implied behavior, constituting a serious inconsistency. Thus, the description fails to disclose behavioral traits consistent with annotations.

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 conveys the core purpose and sample return data without unnecessary words or redundancy. It is perfectly sized for this simple tool.

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 provides useful context about the return payload (MAC addresses, IPv4, services) which is valuable given the lack of an output schema. It does not address error cases or pagination, but for a simple list operation with one parameter, it offers sufficient context to understand what the tool does and returns.

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 single parameter vpc_id is fully documented in the schema with description 'ОБЯЗАТЕЛЬНОЕ ПОЛЕ - ID VPC' (Required field - VPC ID), providing 100% coverage. The tool description adds no additional parameter semantics beyond what the schema already specifies, so a baseline score of 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?

Description clearly states 'Возвращает список портов VPC с MAC-адресами, IPv4 и сервисами' (Returns a list of VPC ports with MAC addresses, IPv4 and services), providing a specific verb (list) and resource (VPC ports) with additional detail on returned data. It distinguishes itself from sibling tools like list_vpc_services and get_vpc by focusing on ports.

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 the tool is used to retrieve port information for a given VPC, but it does not provide explicit guidance on when to use it versus alternatives or mention exclusions. No alternative tools are named, and no context for selection is given beyond the tool's name and description.

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