List Shopify Orders

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 structurally. The description contributes the returned-data shape ('financial details, line items, and customer info'), which is genuinely useful, but says nothing about pagination, the 250-order cap behavior, or rate limits.

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?

Purpose is front-loaded in the first sentence and the argument list is compact with one line each. Nothing is padded, though the Args block partly restates the schema at the cost of a little redundancy.

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 does take on the job of signaling the return content, and it does so. The main remaining gap is pagination/limit interaction with the date range, which an agent listing large ranges would want to know.

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 coverage is 100%, so the baseline is 3, but the description adds value beyond the schema by marking both date bounds as inclusive and giving a concrete composite example for status_filter ('financial_status:paid fulfillment_status:unfulfilled'), which clarifies the query-filter syntax the schema only hints at.

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?

States a specific verb and resource ('List orders') plus the scope ('within a date range') and what the payload contains. It does not, however, distinguish itself from close siblings like shopify_get_order, shopify_order_count, or shopify_list_draft_orders, leaving the agent to infer the boundary.

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?

There is no explicit when-to-use or when-not-to-use guidance and no mention of alternatives. The required date range implies a bulk listing context, but nothing tells the agent why to pick this over shopify_order_count or shopify_get_order.

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