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

Adds substantial context beyond the annotations: it lists every method with EUR/storefront currency, VAT inclusion, weight band, cheapest method, and cost-reduction options. It also discloses Authorization Bearer/ref handling, anonymous access, and search rate limits.

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?

It front-loads the purpose, but then runs long with semicolon-heavy asides about Apeldoorn pickup, forwarders, freight marketplaces, and the store chat. Those details may be useful business context, but they dilute the invocation-critical information.

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 no output schema, it explains return contents, currency and VAT treatment, auth modes, anonymous use, and rate limits. An agent has enough information to call it correctly and interpret the response.

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 all four parameters are already documented with defaults and package-quantity meaning. The description reinforces mutual exclusivity among ref, products, and weight_kg, but adds little new syntax or constraint detail beyond the schema.

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?

States that the tool returns shipping costs and transport options and explains that it prices an order's cart or supplied products/weight. The core purpose is clear, though the broad phrase 'transport options' and the custom-transport advice stretch beyond the quote action.

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?

Gives concrete selection rules: use the order reference for cart pricing, otherwise supply weight_kg or products; country defaults to the cart or storefront country. It also routes pickup to set_checkout and notes anonymous use, though it does not explicitly exclude other quote-related siblings.

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