List Shopify Draft Orders

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds the set of fields that will be returned, but does not disclose pagination behavior or rate-limit considerations; with annotations carrying the behavioral burden, this is adequate but not rich.

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 two short sentences with zero waste, and the core purpose is front-loaded before the filter examples. Every sentence earns its place.

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 listing tool with three optional parameters and annotations covering safety, the definition is nearly complete: it states the returned fields and gives query filter examples. It could mention pagination briefly or distinguish itself from shopify_list_orders, but the schema and annotations cover the main structural gaps.

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 67%; 'after' and 'query' are documented in the schema, while 'limit' is not. The description adds concrete filter syntax examples for the query parameter, which is helpful beyond the schema's 'Shopify query filter' text, but it does not explain the cursor or limit semantics. Baseline 3 is appropriate.

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 and resource: 'List draft orders,' and adds the returned fields (status, customer info, line items, totals). It is clear but does not explicitly distinguish itself from the sibling shopify_list_orders tool, so it falls short of a 5.

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?

It provides useful query filter examples, but gives no guidance on when to use this tool instead of alternatives such as shopify_list_orders. There is no mention of prerequisites, exclusions, or context for choosing draft orders over regular orders.

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