list_account_orders

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

Annotations already indicate read-only and non-destructive. The description adds authentication method (API key), concurrency limit (max 10), and safe-to-retry note, providing value beyond annotations without contradiction.

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?

Well-organized with clear paragraphs and bullet-like argument descriptions. Every sentence adds value—no fluff. The description is appropriately sized for the tool's complexity.

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 tool's simplicity (3 optional params, no required) and presence of an output schema, the description covers purpose, usage, behavior, parameters, and return structure (orders array and total_items) completely.

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 coverage is 0%, but the description fully explains each parameter: count (with max 1000, default 10), offset (default 0), account (optional, with environment variable naming convention and reference to list_accounts). Adds significant meaning beyond schema.

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 tool lists e-commerce orders across all stores in the account. It uses specific verbs ('list') and resources ('e-commerce orders') and distinguishes from the sibling tool list_store_orders by noting the account-wide scope.

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?

Explicitly advises using this tool for account-wide reporting without iterating stores, and directs to list_store_orders for single-store scoping. Also provides context on manual vs. integrated store types.

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