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

Annotations are all false, so the description carries the burden of telling the agent whether the tool has side effects, requires prerequisites, or is safe to call. It only lists delivery options and the conditional availability of carrier tariffs; it does not disclose whether an order or quote record is created, whether pricing is final, or what happens if the cart/city is invalid.

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 a single efficient sentence that front-loads the main action and then adds the key delivery modes and the carrier condition. No filler is present, though it could be slightly more structured for readability.

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 tool with three parameters, no output schema, and unhelpful all-false annotations, the description is too sparse: it lacks return-format expectations, side-effect clarity, prerequisites, and parameter details. An agent would likely need to call the tool or inspect external docs to use it confidently.

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?

With schema description coverage at 0%, the description must compensate. It maps 'корзина' to cart_id and 'город' to city, but adds no format or meaning beyond the schema property names, and postal_code is entirely undocumented in both the schema and the description.

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 opens with a specific verb and resource: assessing delivery of a cart to a city, listing pickup, store delivery, and carrier tariffs. This clearly distinguishes it from order-creation or product-retrieval siblings such as create_invoice_order and get_product.

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 intended use is implied by the phrasing — estimate delivery for a cart to a city — and the conditional note about transport companies adds context. However, there is no explicit statement of when to choose this over alternatives or when not to use it, such as during checkout or before building a cart.

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