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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description goes meaningfully beyond them by disclosing that each call costs $0.03 paid in USDC on Base via x402 — a material invocation constraint no structured field carries. It also caps transparency around output size ('up to 100 products'), but says nothing about failure behavior for an unknown or non-Shopify store address.

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?

Two sentences, front-loaded with the resource and its scope, followed by the return contents and then the cost constraint. Every clause carries information an agent needs; nothing is padding.

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, the description carries the return-value burden well, spelling out the summary fields and per-product fields. Remaining gaps are minor: no mention of pagination or whether results are truncated at 100, and no note on error/empty behavior for an invalid store address.

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 schema already documents store, max, keyword and onlyOnSale; the description's mention of 'up to 100 products' merely mirrors the max ceiling. It adds no new semantics such as keyword matching scope (title vs. description) or how the price range in the summary is computed, so the 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 names a concrete resource — any Shopify store's catalogue — and enumerates exactly what comes back (store summary plus up to 100 products with pricing, stock, variants, vendor, date added). That is far more specific than a name restatement and clearly distinguishes it from the resale-marketplace siblings (ebay_market, poshmark_search, vinted_search), though it never names or contrasts those alternatives 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 only: an agent can infer this is the tool for pulling a Shopify storefront's catalogue rather than a marketplace listing search. There is no explicit when-to-use/when-not-to-use guidance, and the $0.03 per-call cost is stated but not framed as a decision rule (e.g. 'prefer X for cheap lookups').

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