payouts

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

Annotations already declare read-only, idempotent, open-world, and non-destructive, so the safety profile is covered. The description adds genuinely useful behavior — result ordering and the fields returned — but says nothing about how many payouts 'recent' covers, which Stripe account/currency scope applies, or whether results are paginated.

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?

One sentence, no waste, with the resource and ordering stated up front and the returned fields trailing. Every clause carries information an agent can act on.

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 one-parameter read-only list tool with no output schema, describing the return shape (arrival date, status) plus ordering covers most of what an agent needs. The remaining gap is the unexplained limit parameter and the undefined scope of 'recent'.

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 single parameter (limit, default 10) has 0% schema description coverage, so the description must carry that burden and does not. The word 'recent' hints at a bounded window but never explains that limit caps the number of payouts returned, leaving the only input undocumented in both places.

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 a specific resource (Stripe payouts to the bank) with a clear ordering guarantee (newest first) and lists the fields surfaced (arrival date, status). It implicitly separates itself from payout_breakdown by framing this as the recent-list view, but it never names that sibling explicitly.

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?

There is no statement of when to use this versus payout_breakdown, balance, or cash_forecast, which are the obvious adjacent tools. Usage is only inferable from the word 'Recent' — no exclusions, prerequisites, or alternatives are given.

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