shopify_get_order

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds the pagination behavior of line items ('a page of line items'), which maps to the first/after parameters — useful context beyond the annotations. 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?

A single, front-loaded sentence with no filler; every phrase ('shipping, fulfillment, tracking, a page of line items'') adds scope information. It is concise without being under-specified.

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?

With no output schema, the description's list of returned entities partially documents the return value, but pagination mechanics and the semantics of the required 'store' parameter are undocumented. For an agent to invoke the tool correctly, it must infer what 'store' means (store identifier/domain) from context or the sibling set.

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 compensate for the four undocumented parameters. It loosely maps id to 'order' and first/after to 'line item pagination', but the required 'store' parameter is never explained, and the gid format is left to the schema pattern.

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 opens with a specific verb and resource ('Get order') and enumerates the exact data scope: shipping, fulfillment, tracking, and a page of line items. This clearly signals single-order retrieval as opposed to list tools like shopify_list_orders, though it never names a sibling explicitly.

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 guidance is given on when to prefer this tool over competing siblings such as shopify_order_summary or shopify_list_orders. The only usage signal is the weak implication that you use this when you need full order detail, with no exclusions or alternative routing.

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