Список конфигураторов VPS

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

The description indicates a read-only operation ('Возвращает конфигураторы'), while annotations set readOnlyHint=false, implying the operation may have side effects. This is a direct contradiction with the annotation, misleading the agent about the tool's behavioral safety.

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 consists of two concise, front-loaded sentences. The first states the core function and returned data, the second gives usage guidance. No filler or redundancy.

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 parameterless list tool, the description provides useful context about what is returned and when to use it. However, the contradiction with readOnlyHint creates ambiguity about side effects, and the lack of an output schema leaves the response structure partially unspecified.

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, so schema coverage is 100% by definition. The description adds no parameter-specific semantics, but none are needed; per the rubric, 0 params earns a baseline of 4.

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 the specific verb 'Возвращает' (returns) and identifies the resource 'конфигураторы серверов' with details about CPU/RAM/Disk/Bandwidth/GPU ranges and change steps. The phrase '(не тарифом)' clearly distinguishes it from preset/tariff tools like list_server_presets.

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 explicitly states when to use the tool: 'Используй, если нужно создать VPS с произвольной конфигурацией (не тарифом).' This provides a clear usage context and a when-not case (tariff), but it does not name a specific alternative tool, relying on the implicit sibling list_server_presets.

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