shopify_customer_purchase_summary

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 the output includes total orders, total spent, and products/quantities, indicating it is a read-only operation. However, it does not mention any potential costs, rate limits, or data freshness.

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 sentence, which is concise, but it may be too brief. It front-loads the key information but omits important details like parameter semantics and usage context.

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 the tool has 3 parameters with 0% schema coverage, no output schema, and no annotations, the description is insufficient. It does not provide enough context for an AI agent to correctly select and invoke the tool, especially considering the variety of sibling tools.

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 0%, so the description must add meaning. It does not explain the parameters 'customerId', 'email', or 'limit' beyond their names. For instance, it is unclear whether both customerId and email are needed or are alternatives, and what the limit parameter controls (e.g., number of products or orders?).

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 it provides a purchase summary for one customer, including total orders, total spent, and products with quantities. This distinguishes it from sibling tools like shopify_list_customers (which lists customers) and shopify_top_customers (which ranks high-value customers).

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 the tool is for retrieving a purchase summary for a single customer, but it does not explicitly state when to use it versus alternatives like shopify_sales_by_customer_product or shopify_top_customers. No guidance on prerequisites or when not to use.

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