Список серверов

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

Adds concrete return-field context beyond annotations (ID, name, status, etc.) and clarifies account-wide scope. Annotations already cover mutation/destructive hints, so description complements without 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?

Two tightly written sentences; first sentence is front-loaded with the action and return values, second gives practical guidance. No filler.

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 no-param list operation, the description covers what it returns and when to use it, sufficient for an agent to select and invoke correctly. Output schema absent, but the listed fields provide the needed expectation.

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?

Tool has zero parameters, so schema coverage is complete; description is not required to explain parameters. Baseline for zero-param tools applies.

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 specifies a concrete action ('Возвращает список') and resource ('всех VPS-серверов аккаунта'), listing key return fields. It differentiates from sibling project-scoped list tools by emphasizing account-level scope.

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?

Explicitly instructs to use before any server operation to obtain the server ID, providing a clear use case. Lacks explicit alternatives or exclusions.

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