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

The annotations already establish readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds scope context (CZ/SK region, EU reverse charge) but never says whether these are static published policies or live quotes, nor anything about freshness or return shape. With annotations carrying the behavioral load, a 3 is appropriate.

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 dense fragment with no filler, and the most commonly needed content (carriers and prices) is front-loaded. The parentheticals are compact, though the whole thing reads as a noun list rather than a sentence, which slightly weakens orientation.

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 zero-parameter reference tool with no output schema, the content inventory is a good proxy for what comes back, and annotations cover safety. The one meaningful omission is whether the data is static policy versus live carrier rates, which affects whether the agent should re-call it.

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 takes zero parameters, so there is nothing for the description to disambiguate; the empty schema is self-explanatory. Baseline 4 applies.

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?

Enumerates concrete resources: shipping carriers and prices for CZ/SK, the free-shipping threshold, payment methods, the COD fee, B2B EU reverse-charge invoicing, and terms/contact links. That is specific enough to separate it from the sibling tools, which all deal with products and availability. It lacks an explicit verb ('returns'/'describes'), so the action is inferred rather than stated.

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?

There is no explicit when-to-use, no exclusions, and no named alternative. Usage is strongly implied by the name and the content list (call it for shipping cost, payment option, or invoicing questions), which makes it usable but not guided.

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