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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, and the description adds real value beyond them: 'Unknown shipping is not free shipping' warns against a specific misinterpretation of the returned totals, and 'Results do not guarantee stock or checkout prices' discloses data staleness. It does not cover freshness windows or rate limits, but the caveats given are exactly the kind of behavioral context annotations cannot convey.

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?

Four short sentences, front-loaded with the action and scope, then the comparison semantics, then the two caveats. No sentence restates the name or title, and nothing could be removed without losing a distinct point.

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 explained, and the annotations cover safety and openness. Combined with the caveats about shipping and stock, the definition is sufficient to invoke the tool correctly; only the absence of any routing to sibling tools for related pricing questions keeps it from a 5.

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 50%, so the description must do some work, and it does: 'item prices and reported shipping totals' clarifies the item vs. delivered distinction behind price_basis, and 'Unknown shipping is not free shipping' tells the agent that a missing shipping figure is not zero when choosing or interpreting that basis. It says nothing about the language parameter's effect on results or about set_id beyond context, leaving part of the gap unfilled.

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 opens with a specific verb and resource: 'Find monitored retailer offers for one set in a supported market,' and follows with what is compared (item prices and reported shipping totals). The single-set scope distinguishes it implicitly from compare_sets and get_price_history, but no sibling is named explicitly.

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?

Usage is implied by the single-set, single-market framing ('for one set in a supported market'), and the schema tells the agent to ask when the market is unknown. There is no explicit when-to-use/when-not guidance and no pointer to assess_deal, compare_sets, or find_alternatives for related questions such as 'is this a good price?' or 'what else fits?'.

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