Report Shopify Fulfillment SLA Breaches

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds the grouping behavior and SLA threshold context, but does not disclose output format, pagination, or potential edge cases, so it adds moderate value beyond the 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 sentence that is front-loaded with the core action and includes the key configurable SLA aspect. It is efficient and has no redundant wording, though it could marginally benefit from a brief mention of output or scope.

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 schema's rich parameter documentation and the read-only annotations, the description is mostly adequate for an agent to decide to call this tool. However, without an output schema, it does not describe what the report contains (e.g., age buckets or breach counts), which is a gap for an agent needing to interpret results.

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 all four parameters (first, stores, slaDays, lookbackDays) are already documented in the schema. The description adds no additional parameter-level detail, and with full schema coverage, a baseline of 3 is appropriate.

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 objective ('identify orders older than a configurable fulfillment SLA'), which distinguishes it from sibling tools like shopify_list_unfulfilled_orders. The verb and resource are explicit and not tautological.

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 its use for SLA breach reporting, but it does not explicitly state when to use this tool over alternatives such as shopify_list_unfulfilled_orders or shopify_order_summary. There is no direct comparison or exclusion, leaving the agent to infer the best choice.

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