Summarize Orders Across Shopify Stores

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

Annotations already declare readOnly, open world, idempotent, and non-destructive behavior. The description adds useful context beyond annotations by specifying that currency totals remain separate and by enumerating the financial and fulfillment dimensions summarized. This enriches the agent's understanding of what the tool actually returns.

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 two concise sentences. The first sentence front-loads the core purpose and the exact order metrics included, while the second adds a crucial, non-obvious behavioral detail about currency separation. 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?

No output schema is present, but the description clearly names the categories of data summarized and flags currency behavior. Annotations cover the safety/idempotency profile. The only notable omission is the exact response shape, but for a summary tool this is less critical given the explicit metric list.

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%, and the description adds no parameter-level detail beyond what the schema already documents. The 'days' and 'first' parameters are well defined in the schema, so the description does not need to compensate. It maps 'across selected stores' to the stores parameter but without extra syntax or formatting detail.

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 uses a specific verb and resource: 'Summarize recent order values, discounts, shipping, tax, cancellations, and financial and fulfillment statuses across selected stores.' This clearly distinguishes it from list/get order tools by emphasizing aggregation across stores, while still naming concrete order dimensions.

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 clearly signals when this tool is appropriate: for high-level multi-store order summaries rather than per-store order lists or single-order lookups. It does not explicitly name alternatives like shopify_list_orders or state exclusions, but the aggregation context is clear enough for an agent to route correctly.

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