get_amazon_transactions

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

With no annotations, the description carries the full burden. It reveals the fetch behavior, the layout handling, and the return fields. It does not mention potential side effects or rate limits, but for a read-only operation this is acceptable and there is no 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?

The description is concise, with two clear sentences plus a list of returned fields. It avoids unnecessary detail while still providing useful context.

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, the description provides enough context: it states what is fetched, the returned fields, and the layout support. Though there is no output schema, the listed fields give a reasonable expectation of the result. Minor gaps like value formatting are not critical.

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 covers all four parameters with descriptions. The description does not add extra meaning beyond what is already in the schema—such as the enum values for region or the meaning of max_scrolls—so a baseline score of 3 is appropriate.

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 the verb 'Fetch' and the resource 'Amazon payment transactions', distinguishes from per-order extraction, and lists the returned fields. This differentiates it from sibling tools like get_amazon_orders and get_amazon_order_details.

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?

Provides context on when to use it ('faster than per-order extraction') and mentions support for paginated and infinite-scroll layouts. However, it does not explicitly name alternatives like export_amazon_transactions_csv or state when not to use it, so it falls short of full explicitness.

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