export_amazon_gift_cards_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 describes what the tool does (export to CSV) and lists the CSV columns, which helps understand the output format. However, it doesn't mention authentication requirements, rate limits, whether it's a read-only operation, or potential side effects like file system changes. The description adds some value but leaves important behavioral aspects unspecified.

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 perfectly concise with two sentences that each serve distinct purposes: the first states the core functionality and output format, the second provides usage context. Every word earns its place with no redundancy or unnecessary elaboration.

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 (export operation with 3 parameters), no annotations, and no output schema, the description does a good job covering the essentials: what it does, what the output contains, and when to use it. However, it doesn't address authentication requirements or potential limitations (like pagination behavior implied by max_pages parameter), which would be helpful given the lack of 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 three parameters thoroughly. The description doesn't add any parameter-specific information beyond what's in the schema, but with complete schema coverage and only 3 parameters, this is acceptable. The baseline would be 3, but the description's clarity about the overall purpose and output format elevates it slightly.

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 gift card transaction history to CSV file') and distinguishes it from siblings by focusing on gift cards rather than items, orders, shipments, or general transactions. It explicitly mentions the resource (Amazon gift cards) and output format (CSV).

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 about when to use this tool ('Useful for tracking gift card usage and reconciling balances'), which differentiates it from siblings like get_amazon_gift_card_transactions (which likely returns data without exporting). However, it doesn't explicitly state when NOT to use it or name specific alternatives for different scenarios.

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