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

With no annotations, the description carries full burden. It doesn't disclose side effects (if any), return format, or prerequisites beyond 'model'. It does mention delivery calculation, but lacks explicit read-only confirmation, whether it produces a breakdown, or any required parameters beyond what's obvious.

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 short sentences, front-loaded with the primary purpose, and no redundant information. Every word contributes to understanding what the tool does.

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 7-parameter tool with no output schema or annotations, the description is adequate but incomplete: it doesn't mention the include_furniture parameter, doesn't specify the return value (e.g., total price, breakdown), and lacks any guidance on how to interpret 'под ключ'. The base purpose is clear, but these gaps could cause an agent to overlook options or misjudge outputs.

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%, so baseline is 3. The description adds value by mapping the listed kit components (filtration, cover, border, delivery) to the boolean include_* parameters and the city parameter, making the relationship between description and schema clearer.

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 calculates the cost of a turnkey kit (pool + filtration + cover + border + delivery). The verb 'расчёт' and the resource 'комплект' are specific, and the component list distinguishes it from sibling tools like get_pool_price or get_filters.

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 implies usage for bundled quote calculations, but does not explicitly state when to use this vs alternatives like get_pool_price or get_accessories. No exclusions or alternative tool names are mentioned, though the component list hints at the intended scenario.

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