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

Annotations already establish this as a safe read, and the description piles on genuinely useful behavior: what profitability excludes (ad spend, FBA storage, inbound freight, COGS, Adjustment/ServiceFee events), how MCF fees are segregated from total_fees/net_profit, the posted_date vs order-date distinction, data_gap flags, and the currency-mixing hazard of include_all_currencies.

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 opening sentence is appropriately front-loaded, but the body is a single dense block with reconciliation caveats, exclusion lists, and cross-references interleaved rather than grouped. Nearly every clause carries information, yet the flat structure makes it hard to scan for the one or two facts an agent needs for a given call.

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?

For a 13-parameter, multi-mode read tool with an output schema and full annotation coverage, the description supplies the scoping, exclusion, reconciliation, and currency semantics an agent needs to interpret results correctly. The remaining mechanics (sort columns, pagination offsets) are already handled by the schema and need no restatement.

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% and each parameter is already documented, so the baseline is 3; the description goes beyond it by explaining the view/grain interaction (grain only matters when order_id is omitted), the meaning of include_all_currencies summing risk, and which money fields each view emits. It does not add format or syntax detail for the date/pagination params, keeping it just short of a 5.

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 names the specific resource (Finances v0 financial-event rows plus ASIN economics) and enumerates the two views and three grains, so an agent can tell exactly what the tool returns. It also explicitly disambiguates from siblings by naming get_payment_transactions and get_settlement_economics with the conditions that select them.

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?

It states when each mode applies ('view=fee_breakdown' with order_id vs date-range grains; 'profitability' for ASIN economics) and gives explicit when-not routing: pre-settlement rows go to get_payment_transactions and finalized settlements to get_settlement_economics. Alternatives and their selecting conditions are spelled out rather than implied.

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