shopify_list_abandoned_checkouts

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

No annotations are provided, so the description carries the full burden. It indicates the output includes cart subtotals and customer context, and that results are 'recent,' but does not state read-only nature, required permissions, or rate limits. Some transparency, but gaps remain.

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 paragraph plus an Args list, with the purpose front-loaded. It is concise and avoids fluff, though the Args section somewhat duplicates schema information but adds necessary detail.

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 that an output schema exists, the description need not detail return values. Parameters are covered adequately, and the use case is clear. Minor gaps like pagination or error handling are acceptable for a list tool with limit.

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?

With schema description coverage at 0%, the description compensates well. It adds value by specifying the valid range for 'limit' (1-250) and providing an example for 'query' ('created_at:>=2026-04-01'). Both are meaningful beyond the schema's type and default.

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 'List the shop's recent abandoned checkouts with cart subtotals and customer context,' using specific verb and resource. It is easily distinguishable from sibling list tools like shopify_list_collections or shopify_list_draft_orders.

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 includes the explicit use case: 'Use to compute abandoned-revenue at risk and prioritise recovery.' It does not explicitly mention when not to use or alternatives, but the use case is clear and contextually relevant.

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