list_presets

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

Annotations already declare readOnlyHint=true, and the description adds a useful behavioral detail: 'Токен не требуется' (token not required). It does not describe pagination or response format, but for a read-only listing tool the annotation covers safety and the token note adds operational context.

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 two short sentences: the first front-loads the main purpose and scope, the second adds the auth requirement and usage context. There is no fluff or repetition of schema details.

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 one-parameter read-only list tool, the description covers what is returned (available instant-servers with prices), where (specified location), auth requirements, and when to use it. With readOnlyHint and openWorldHint annotations, nothing essential is missing.

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% and the single parameter 'location' is already documented with its allowed values. The description only repeats 'in the specified location' without adding deeper meaning to the parameter, so the baseline 3 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?

The description states a clear verb ('list') and resource ('available instant-servers (VM/BM/GPU/vGPU) with prices in a specified location'), so an agent can understand the core function. It does not explicitly distinguish this from sibling tools such as search_presets or get_preset_pricing, so it falls short of full differentiation.

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 gives explicit usage context: 'Нужен для подбора preset перед заказом' (needed for choosing a preset before ordering). It does not mention exclusions or when to prefer an alternative like list_preset_groups or search_presets, so it is clear context but lacks alternatives.

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