Compare Shopify Catalogs

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 carries a lighter burden. It does add the behavioral detail that comparison is keyed to 'exact handles', implying exact-match semantics rather than fuzzy search. However, it does not disclose what happens when a handle is absent from one of the stores or how missing data is represented in output.

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?

A single 22-word sentence with no filler. The verb is front-loaded, the compared fields are enumerated compactly, and the cross-store scope is stated at the end. Every word earns its place.

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 tool with full schema coverage and rich annotations, the description is minimally viable: an agent knows what to pass and that the call is safe. But with no output schema, the description does not clarify the return shape or how missing handles across stores are reported, which matters for interpreting comparison results.

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 both parameters; the baseline is 3. The description adds modest value by clarifying which product attributes will be compared for the given handles, but it does not explain store alias resolution or handle matching behavior beyond what the schema provides.

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 states a specific verb ('Compare'), a precise resource (product titles, status, vendor, product type, and inventory for exact handles), and a clear scope (across multiple Shopify stores). The listed field set distinguishes it implicitly from siblings like shopify_compare_collections, shopify_compare_prices, and single-store get/search tools.

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?

No when-to-use or when-not-to-use guidance is provided, and no alternatives are named. Given overlapping siblings such as shopify_compare_inventory, shopify_compare_prices, and shopify_get_product_everywhere, an agent has no way to know which cross-store comparison tool to select for a given task.

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