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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses the return payload (links, live stock, prices, descriptions, feature excerpts), that shortlisted reads happen concurrently, the scope limit (stores exposing a public Shopify catalog), and that errors explain the fallback. No contradiction with readOnlyHint. It stops short of noting rate limits or result freshness/caching.

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?

Five sentences, front-loaded with the primary purpose and followed by filtering behavior, return contents, and the citation instruction. Mostly earns its place, but the opening keyword list and the 'supports stores exposing a public Shopify catalog' sentence 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?

With no output schema and 6 parameters at 67% schema coverage, the description does the necessary work: it explains what one call returns, the Shopify-only scope, and error behavior, plus a downstream citation requirement. Minor gaps remain on currency/limit semantics, but nothing required to invoke it correctly 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 coverage is 67%, and the description reinforces the two most error-prone parameters: it stresses 'exact size' (matching the schema's 'never substitute another size') and clarifies max_price is an exclusive ceiling. It adds no meaning for audience, limit, or currency, which the schema already partially documents — marginal but real added value.

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?

States a specific verb and resource — filters the public store catalog by variant availability, exact size and price ceiling, then reads shortlisted product details — and the title names the outcome (in-stock products, price comparison). It is distinguishable from siblings like search_site or read_page, though the opening clause ('shopping, shoes, product comparisons and recommendations') is keyword-stuffed rather than precise.

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?

Explicitly positions itself as the 'FIRST tool for shopping' and says to use it 'instead of guessing product names or repeated research/search/read calls,' which points at sibling tools without naming them. It lacks an explicit when-not condition (e.g., for non-Shopify stores beyond the fallback error note), so it falls short of a 5.

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