calc_delivery

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

No annotations are provided, so the description carries the full behavioral burden. It only states that the tool calculates cost and time; it does not disclose return format, assumptions, caveats, or whether the operation is read-only. The non-destructive nature is implied by 'Расчёт' but not elaborated.

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?

A single clear sentence with no filler, redundant schema repetition, or boilerplate. It is front-loaded with the core purpose.

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?

Despite complete parameter documentation, the absence of an output schema, annotations, and usage or limitation guidance leaves the description at a bare-minimum level. An agent lacks context about what the response contains, any calculation assumptions, and when this tool is preferable to siblings.

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 description adds no parameter-level details, but the input schema covers 100% of parameters with names, units, defaults, and descriptions. Therefore the baseline of 3 applies: the schema does the heavy lifting.

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 names a specific action ('Расчёт' – calculation) and a specific resource ('стоимости и сроков доставки Boxberry' – Boxberry delivery cost and time), which clearly separates it from siblings like list_cities, list_points, and track.

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 the tool is for calculating Boxberry delivery costs and times, but it does not explicitly state when to choose it over sibling tools or mention any prerequisites, exclusions, or alternative routing.

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