Shopify MCP Server

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

With no annotations provided, the description carries the full burden. It discloses that the tool retrieves data (read-only implied by 'Get'), lists returned fields, and mentions filtering support. However, it lacks details on permissions, rate limits, pagination beyond the 'first' parameter, or error handling, leaving behavioral gaps for a tool with no annotation coverage.

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 front-loaded with the core purpose, followed by details on returned data and filtering. It uses two efficient sentences with zero waste, making it easy to scan and understand without unnecessary elaboration.

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 read-only tool with no annotations and no output schema, the description adequately covers the purpose and basic behavior. However, it lacks details on output format (e.g., structure of returned data), error cases, or advanced usage scenarios, which could be important given the tool's complexity and lack of structured output documentation.

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 fully documents all three parameters. The description adds minimal value beyond the schema by mentioning filtering by SKU or product title, which aligns with the 'query' parameter's description. No additional syntax or format details are provided, resulting in a baseline score of 3.

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 clearly states the verb ('Get') and resource ('inventory levels for products/variants'), specifying what data is retrieved. It distinguishes from siblings by focusing on inventory rather than sales, customers, or other metrics, making its purpose specific and unambiguous.

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 description implies usage for inventory-related queries but does not explicitly state when to use this tool versus alternatives like sales or order tools. It mentions filtering capabilities but lacks guidance on prerequisites, exclusions, or direct comparisons to sibling tools, leaving usage context somewhat inferred.

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