list_online_orders

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

No annotations provided. The description mentions default date ranges but does not disclose side effects, idempotency, rate limits, or authorization requirements. Assumed read-only but not explicit.

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-structured with summary, return description, and parameter list. Slightly verbose on parameter details but clear and easy to parse.

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?

Covers purpose, parameters, and returns. Lacks error handling, pagination behavior, or output schema details beyond what is stated. Output schema exists but description is sufficient for common usage.

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 has 0% description coverage; the description provides format, defaults, and purpose for all 6 parameters, greatly exceeding schema info.

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?

Clearly states listing online Costco.com orders for a date range, differentiating from sibling tools like get_receipt_detail and list_warehouse_receipts.

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?

Describes the use case but does not explicitly state when not to use or mention alternative tools. Sibling names are provided but not referenced in the description.

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