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

The annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavioral context beyond that: two specific carriers, a fixed origin warehouse, and a pickup option that is free but only by prior arrangement.

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?

Three short sentences, front-loaded with what is returned (cost and timeframes) then how to call it, then the pickup caveat. No filler, though the pickup sentence is only marginally relevant to a quote call.

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 read-only quote tool with full schema coverage and no output schema, the definition covers purpose, origin, carriers, input choice and the pickup fallback. It does not state whether the result is a binding price or an estimate, nor anything about currency or validity period, which is the main remaining gap.

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 every parameter already carries its own description, and the baseline is 3. The description reinforces the either/or between items and weight_kg, but adds no format, unit, or edge-case detail beyond what the schema states.

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 specific verb and resource: cost and timeframes of delivery via two named carriers (СДЭК, Деловые Линии) from a fixed origin (Дмитров). Combining this with the neighboring quote_cart tool is easy to distinguish by the fixed origin and the item/weight input, though the definition never names that alternative explicitly.

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 input guidance that implies usage ('Передайте товары (items) или вес'), and the free-pickup note implies a scenario where delivery isn't needed. Alternatives are not named and no when-not condition is spelled out.

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