export_amazon_transactions_csv

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explains the extraction method ('Extracts transaction data from each order's detail page'), which adds useful context beyond the basic 'export' action. However, it lacks details on permissions needed, rate limits, error handling, or whether the operation is idempotent, leaving gaps for a mutation-like tool (exporting files).

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 implementation details and a clear alternative. Both sentences earn their place: the first defines the tool and its output format, the second provides critical usage guidance. No wasted words or redundancy.

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 complexity (6 parameters, file export operation) and no output schema, the description does well by specifying the CSV columns and extraction method. However, it could better address behavioral aspects like file overwriting or error scenarios. With no annotations, it's mostly complete but has minor gaps in operational transparency.

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?

The schema description coverage is 100%, so all parameters are documented in the schema itself. The description does not add any parameter-specific details beyond what's in the schema (e.g., it doesn't explain the relationship between 'year' and 'start_date/end_date' or clarify 'max_orders' behavior). Baseline 3 is appropriate as the schema handles the heavy lifting.

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 payment transactions to CSV file') and resource ('transaction data from each order's detail page'), distinguishing it from sibling tools like 'export_amazon_orders_csv' or 'export_amazon_items_csv' by focusing specifically on payment transactions. It provides concrete details about the CSV columns, making the purpose unambiguous.

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 explicitly provides when to use this tool vs. alternatives by stating 'For faster bulk transaction export, consider get_amazon_transactions which scrapes the dedicated transactions page.' This gives clear guidance on choosing between detailed extraction from order pages vs. faster bulk export, addressing a key decision point for users.

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