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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the description's job is to add context. It does: supplying an item name changes the output by adding today's-price links, which is a non-obvious behavioral trait. It doesn't mention latency, coverage limits, or what a policy-less store returns.

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?

The opening sentence is a verbatim duplicate of the title, which is pure waste. The example list is long but genuinely aids intent matching, and the scoping line about item names is useful, so the description is functional rather than bloated.

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 lookup with only three fully documented parameters and no output schema, the description supplies enough to call the tool correctly and even hints at the shape of the result when an item is given. It could say more about what the policy payload contains, but nothing required is missing.

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 all three parameters are already documented in the schema, including the item parameter's link-adding behavior. The description merely restates that behavior and adds nothing on store or country syntax, so the baseline of 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 names the specific resource (a store's price adjustment and price match policy) and anchors it with concrete natural-language queries an agent can match intent against. It does not, however, distinguish itself from the sibling check_price_drop_claim, which the example "will Costco refund the difference?" could plausibly belong to.

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?

The example phrasings give a clear, practical picture of when to reach for this tool over a general store lookup. It stops short of stating any when-not condition or naming an alternative tool for claim checking, so the boundary with check_price_drop_claim remains implicit.

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