Report Shopify Fulfillment SLA Breaches

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

Annotations already declare the tool read-only, idempotent, and non-destructive. The description adds meaningful behavior beyond that: it scopes to open unfulfilled orders, groups them into age buckets, and applies a configurable SLA threshold. No contradiction with annotations.

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, front-loaded sentence with no filler. It efficiently communicates both the grouping behavior and the SLA breach detection purpose.

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?

The schema and annotations are strong, but there is no output schema and the description does not describe the report's return structure. Usage guidance relative to similar order/report tools is also missing. Enough to invoke correctly, but not complete for an agent deciding which report to use.

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 baseline is 3. The description echoes 'selected stores' and 'configurable fulfillment SLA', which map to stores and slaDays, but does not add meaningful detail beyond the schema because all parameters are already documented.

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 states a specific action ('Group open unfulfilled orders into age buckets') and a clear goal ('identify orders older than a configurable fulfillment SLA'). This distinguishes it from list-oriented siblings such as shopify_list_unfulfilled_orders and other report tools.

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?

No sentence explains when to prefer this report over siblings like shopify_list_unfulfilled_orders or shopify_order_summary, nor any exclusions. The agent must infer usage from the title and sibling names.

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