export_amazon_orders_csv

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

With no annotations provided, the description carries the full burden and does well by disclosing performance traits ('~0.5s per 10 orders'), output details (CSV columns and default save location), and operational constraints (batching advice for large accounts to avoid timeouts). It doesn't mention authentication requirements or error handling, leaving some gaps.

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 front-loaded with the core purpose, followed by performance details, output specifics, and usage advice in three efficient sentences. Every sentence adds value without redundancy, making it appropriately sized and well-structured.

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 moderate complexity (6 parameters, no output schema, no annotations), the description is largely complete: it covers purpose, performance, output format, defaults, and scaling advice. However, it lacks details on authentication, error cases, or what happens on failure, which would be helpful for a tool with no annotations.

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 100%, so the schema already documents all parameters thoroughly. The description adds marginal value by explaining the default filename pattern and batching recommendation for max_orders, but doesn't provide additional semantic context beyond what's in the schema descriptions.

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 specific action ('Export Amazon orders summary to CSV file') and resource ('Amazon orders'), distinguishing it from siblings like export_amazon_items_csv or export_amazon_transactions_csv by focusing on orders summary rather than items, transactions, or other data types.

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 clear context for when to use this tool ('Fast extraction from order list page') and includes an explicit alternative for large accounts ('use max_orders to batch exports and avoid timeouts'), but it doesn't explicitly state when NOT to use it versus other sibling tools like get_amazon_orders or export_amazon_items_csv.

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