Список ПО из маркетплейса

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

The description states the tool 'returns a list' (read operation), but the annotation readOnlyHint=false implies the operation may not be read-only. This is a direct contradiction. No other behavioral details like permissions or side effects are disclosed, but the contradiction mandates a score of 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 two concise sentences, front-loaded with the essential purpose and followed by actionable guidance. No wasted words.

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?

With no output schema, the description adequately conveys the return fields (ID, name, os_ids, requirements) and the use case (selecting software_id during VPS creation). This is sufficient for an agent to understand the tool's role and output.

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 there is no need for parameter explanation. The description adds context about what the output contains, effectively compensating for the lack of an output schema.

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 identifies the tool as returning a list of marketplace software available for VPS installation, with specific fields (ID, name, os_ids, requirements). It distinguishes itself from sibling list tools like list_server_os and list_server_presets by scoping to marketplace software.

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 includes an explicit usage directive: 'Используй, чтобы выбрать software_id' (Use to select software_id). This indicates when to use the tool, though it does not mention alternatives or exclusions. The context is clearly for VPS creation setup.

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