Список тарифов VPS-серверов

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

The description implies a read-only operation ('returns all available tariffs'), but the annotation readOnlyHint=false indicates the tool may not be read-only. This is an annotation contradiction. No other behavioral context is provided, so the score is 1.

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 three sentences with clear structure: what it returns, when to use, and explicit exclusion of application presets. No redundant information.

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 with no output schema, the description is fairly complete: it names the returned fields, provides usage context, and disambiguates from a related tool. It lacks note about pagination or authorization, but those are not apparent from the schema; the annotation contradiction slightly reduces completeness.

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 the baseline is 4. The description adds value by enumerating the output fields (ID, price, location, CPU, RAM, disk, disk type, bandwidth) which is helpful despite the absence of parameters.

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 all available tariffs (presets) for VPS servers' and lists specific attributes (ID, price, location, CPU, RAM, disk, disk type, bandwidth). It also explicitly distinguishes itself from application presets by naming the alternative tool get_allowed_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?

It explicitly says 'Use before creating a VPS to select preset_id' and clarifies 'NOT presets for applications — for those there is get_allowed_presets', providing both when-to-use and when-not-to-use guidance with a named alternative.

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