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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world hint, so the safety profile is covered. The description adds useful non-structured context that these are exactly the checkout prices on whoppah.com, but says nothing about pricing volatility, geographic limits, or what happens when no shipping is available.

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?

Two tight sentences with the resource and the invocation details front-loaded, and no filler. The example country code is compact and directly actionable.

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?

An output schema exists, so return values need not be spelled out, and the description tellingly enumerates the option types (courier, parcel, pickup). The only real gap is the unmentioned optional postal_code argument, which is minor for a quote lookup.

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 description coverage is 0%, so the description must carry the load. It clarifies product_id and country with a format example ('de'), which is genuinely useful, but it entirely omits postal_code, one of three parameters, leaving that argument undocumented.

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 resource and scope: shipping options and prices for one listing to the buyer's country, including the carrier formats (courier, parcel, pickup). It is clearly distinct from siblings like get_item or search_catalog, though it never explicitly names an alternative.

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?

It gives the concrete invocation recipe (product id plus a country code with a lowercase example) and ties the result to what checkout shows on whoppah.com. However, it offers no when/when-not guidance relative to the other retrieval tools, so usage is only implied.

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