shopify_list_draft_orders

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

With no annotations, the description should disclose behavioral traits but only states basic functionality. It omits details about pagination, rate limits, default behavior, or whether results are limited, which is critical for agent usage.

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 concise with one sentence and an arg list, avoiding unnecessary verbiage. However, it lacks a structured format that separates overview from parameter details.

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?

Given the simple nature of a list operation and the presence of an output schema, the description provides minimal necessary context. It fails to mention default behavior or result format, leaving room for ambiguity.

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%, but the description adds value by specifying valid values for 'status' ('One of: open, invoice_sent, completed'). However, 'limit' is merely listed with no explanation, leaving gaps in parameter understanding.

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 'List draft orders from the connected Shopify store,' using a specific verb ('List') and resource ('draft orders'), and distinguishes it from sibling tools that deal with discounts, fulfillment orders, etc.

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 no guidance on when to use this tool versus alternatives like shopify_list_fulfillment_orders or shopify_list_discounts. There is no mention of use cases, exclusions, or when not to use it.

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