Shopify MCP Server

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

No annotations are provided, so the description carries full burden. It mentions what metrics are shown but doesn't disclose behavioral traits like whether this is a read-only operation, requires specific permissions, has rate limits, returns aggregated vs detailed data, or handles pagination. 'Get' implies reading, but lacks operational context.

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 appropriately sized with two concise sentences that directly address purpose and scope. It's front-loaded with the core function and avoids any unnecessary elaboration, making every sentence earn its place efficiently.

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?

Given no annotations and no output schema, the description is moderately complete for a read operation but has gaps. It covers what metrics are retrieved but lacks details on return format, error handling, or behavioral constraints, which are important for a tool with three parameters and no 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 already documents all parameters thoroughly. The description adds no parameter-specific information beyond what's in the schema, maintaining the baseline score of 3 where schema does the heavy lifting.

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 tool's purpose: 'Get customer acquisition and behavior metrics' specifies the verb and resource, and 'Shows new vs returning customers over time' adds scope. It distinguishes from siblings like sales or inventory tools, though not explicitly from all customer-related alternatives.

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 provides no guidance on when to use this tool versus alternatives. With siblings like shopify_custom_query or shopify_sales_summary that might overlap, there's no indication of when this specific customer metrics tool is preferred or what prerequisites might apply.

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