get_order_financial_events

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

With no annotations provided, the description bears the full burden. It discloses the return structure (sale amount, fees, taxes, shipping, adjustments) and implies it is read-only. It does not discuss pagination or authorization, but the schema adds pagination details. Overall adequate for a read operation.

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?

Two sentences, no extraneous information. First sentence states core purpose, second adds return detail. Efficient and front-loaded.

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 no output schema, the description explains the return content well. It lacks mention of pagination or response structure, but the schema includes nextToken. For a relatively simple tool with three parameters, it is mostly complete.

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 coverage is 100%, so the description adds little beyond the schema for individual parameters. However, the overall description helps contextualize the parameters by stating what the tool returns, which is useful but not extensive.

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 it retrieves financial events for a specific Amazon order, using a specific verb ('Get') and resource ('financial events'). It also distinguishes from broader sibling tools like get_financial_events by tying to an order ID.

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 says when to use this tool (for a specific order's financial events). However, it does not provide explicit exclusions or mention alternatives among sibling tools, though the context of requiring orderId implies order-specific use.

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