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 of behavioral disclosure, yet it only says 'List orders.' It implies a read-only operation but says nothing about pagination behavior (limit defaults to 50, max 250), result ordering, or response shape. There is no annotation contradiction since no annotations exist.

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 five-word sentence that front-loads the action verb and resource with zero wasted words. It is efficient and well-structured, though arguably too terse for a tool with 4 parameters and no annotation support.

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 tool with no annotations, no output schema, and 0% parameter coverage, this minimal description leaves too much unstated: default limit behavior, pagination implications, and the relationship to shopify_get_order. The schema defines the parameter space, but the description adds little beyond the core operation.

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, but it only refers generically to 'filtering options' without explaining any parameter. The enum names (status, financial_status, fulfillment_status) are moderately self-explanatory, yet the description itself adds no semantic detail beyond what the property names convey.

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 verb ('List') and resource ('orders'), and the phrase 'with filtering options' hints at the parameterized nature of the tool. It is clearly distinct from shopify_get_order by the plural/singular convention, though it does not explicitly call out that distinction.

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 guidance on when to use this tool versus shopify_get_order or the other list tools. 'With filtering options' implies filtered retrieval of orders, but no usage conditions, exclusions, or alternative routing are provided.

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