Compare Shopify Inventory

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds context about the scope of comparison but does not disclose additional behavioral traits such as output structure, pagination, or store-alias requirements. No contradiction with annotations exists.

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 description is a single efficiently worded sentence that leads with the main verb and captures the core scope without any filler. Every word contributes to meaning, making it well suited for quick agent parsing.

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?

The description is adequate for a relatively simple two-parameter comparison tool with strong annotations, but no output schema exists and the description does not mention what the response looks like. It also leaves 'catalog details' vague and does not help the agent distinguish this from other comparison tools, leaving some contextual gaps.

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%, with clear descriptions for both skus (1–50 exact SKUs) and stores (1–100 configured aliases). The tool description adds no parameter-specific meaning beyond what the schema already provides, 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 states a specific verb (Compare) and resource (inventory, price, product status, catalog details for selected SKUs across multiple Shopify stores). This clearly conveys the core function. It does not explicitly differentiate from overlapping siblings like shopify_compare_catalog or shopify_compare_prices, so it stops short of a 5.

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 intended use case is implied: comparing multiple attributes for chosen SKUs across several stores. However, there is no explicit guidance on when to use this tool instead of the many related sibling tools, nor any stated exclusions or prerequisites. The presence of overlapping tools like compare_catalog and compare_prices makes this a noticeable gap.

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