shopify_list_orders

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

No annotations are provided, so the description should disclose behavioral traits like read-only safety. It only mentions defaults and query syntax but does not state that the tool does not modify data, nor does it discuss rate limits or pagination cursor behavior. The read-only nature is implied but not explicit.

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 very concise (one sentence) and front-loaded with the primary action and an example. However, the structure could be improved by separating the query example from default info.

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 tool has 5 parameters, no required ones, and no output schema. The description only covers query and first defaults, leaving 'after', 'sortKey', and 'reverse' unexplained. Pagination and sorting details are missing, making it incomplete for an AI agent to use effectively.

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. It explains the 'query' parameter with an example and mentions 'first' default/max, but does not explain 'after' (pagination cursor), 'sortKey' values, or 'reverse'. The added value over the schema is minimal.

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 the tool lists orders and mentions the optional search query with an example. It distinguishes the resource (orders) and verb (list), but does not explicitly differentiate from the sibling tool 'shopify_search_orders', which could cause confusion.

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 provides an example query and default pagination values, but offers no guidance on when to use this tool versus alternatives like 'shopify_search_orders' or 'shopify_get_order'. It lacks when-not-to-use and exclusion criteria.

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