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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: the exact country coverage and an important limitation that US duty depends on product and origin and is only estimated for beauty products, which warns the agent about partial accuracy.

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 sentences, front-loaded with what the tool explains and the domain it covers, then the limitation. No filler, though the mid-sentence country list and the 'how Lowcart counts them in totals' clause could be tightened.

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 one-parameter read-only lookup with no output schema, the description supplies the coverage scope and the key accuracy caveat. It is nearly complete; it does not indicate whether the response is a single rule set per country or a breakdown, but that is a minor gap for this simple tool.

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 100%, so the single 'country' parameter and its 'Two letter country code' format are already documented. The description confirms the country-scoped nature of the tool but adds no format, validation, or defaulting detail beyond the schema, so baseline 3 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?

The description states a specific informational resource — the sales tax, VAT, GST and import duty rules a shopper pays on cross-border goods — and notes how Lowcart counts them in totals. That is clear enough for an agent to know it is a lookup/reference tool, but it never mentions the sibling find_delivered_price or explains how the two differ.

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 statement of when to call this tool versus find_delivered_price, nor any prerequisite or exclusion. The only scoping information ('covers the US, UK, Australia, New Zealand and every EU country') describes coverage, not usage selection, so the agent must infer when this is the right call.

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