shopify_list_orders

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

With no annotations provided, the description carries the full burden. It discloses 'read-only' behavior but omits other critical traits such as pagination, sorting defaults, rate limits, or error handling. This is insufficient for a mutation-free list operation with multiple filter parameters.

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 sentence that is concise and direct, front-loading the main action and output. Although very brief, it avoids fluff and redundant information. Slightly more structure (e.g., bullet points for parameters) would improve scannability but not essential.

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?

For a simple list tool with no output schema, the description covers the core purpose and read-only nature. However, it lacks details on pagination, sorting, or intended use cases. Given the complexity (4 optional parameters) and sibling list tools, more contextual cues (e.g., batch retrieving orders) would be beneficial.

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 only 25% (query parameter has description). The tool description does not add meaning to any parameters; it only mentions output fields. For a tool with 4 parameters, this is a significant gap, especially for createdAfter/createdBefore (date-time format) and limit (default/max).

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 action ('List'), the resource ('Shopify orders'), and the scope ('read-only'), along with output fields (customer, amount, line items). This distinguishes it from sibling tools that are analytical summaries, establishing a specific verb+resource pattern.

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 provided on when to use this tool versus alternatives. For example, there is no mention of when to use list_orders over list_customers or any of the analytical tools. The description does not specify use cases, prerequisites, or exclusions.

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