list_orders

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

No annotations are provided, so the description carries full burden. It does not confirm this is a read-only operation or disclose any side effects. For a listing tool, this is a notable gap.

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 short (two sentences) and front-loads the core purpose. However, it contains inaccurate statements that could mislead, making it less efficient.

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 description lacks critical context such as what data the response contains (order fields) and how to use pagination parameters (since_id, page_info) correctly. Given no output schema, more detail is needed.

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?

While schema coverage is 100%, the description contains inaccuracies: it claims 'Use `status` to filter by fulfillment status' but status actually filters by order status (open/closed/cancelled). It also states 'By default returns open orders' but the schema default for status is 'any'. These errors reduce its helpfulness.

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 orders in the store' with a specific verb and resource. It distinguishes from sibling list tools by mentioning default behavior (open orders) and available filters, making the purpose unmistakable.

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 specifies when to use the tool by noting default returns open orders and suggesting status/financial_status filters. It also mentions pagination. However, it does not explicitly state when to avoid this tool or mention alternatives like get_order for detailed info.

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