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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered elsewhere. The description does add one genuinely behavioral detail — that the result includes the free-shipping threshold — which is useful beyond the annotations. It still omits how the rate is derived (per-country table? weight? basket tiers?) and whether a missing country yields an error or a default, which is the kind of context a pricing tool needs.

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 is a single short sentence with no filler, which is good, but it is an ungrammatical fragment ("shipping price to a country by basket value") that reads like a truncated field label. Brevity is achieved at the cost of parseability, and the free-shipping clause is tacked on rather than structured.

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 two-parameter read-only lookup this is close to adequate, and with no output schema the description does at least hint that the response carries a threshold. However, the dangling "basket value" reference and the absence of any statement about how rates are scoped (store currency, country coverage, fallbacks) leave an agent guessing about what it will actually get back.

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%, with both `store` (including the full store-code list and currency implications) and `country` (ISO alpha-2 examples) fully documented in the schema, so the baseline of 3 applies. The description adds nothing about either parameter and instead references a "basket value" that is not a parameter, which is a mild source of confusion rather than added meaning.

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 fragment "shipping price to a country by basket value, including the free-shipping threshold" does convey the resource (shipping price) and the key input dimension (country), so an agent can roughly tell what it returns. But it never uses a verb, and "by basket value" implies a pricing input that does not exist in the schema, leaving the actual computation ambiguous.

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 when-to-use guidance, no prerequisites, and no mention of alternatives. The sibling list contains nothing shipping-related, so confusion risk is low, but the description does nothing to route the agent or state the context in which a shipping quote is appropriate.

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