stripe_balance_transactions_list

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds the useful detail that each result carries a reporting_category field, but says nothing about pagination behavior, volume limits, or return shape beyond that. Adequate but not rich.

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 filler, and the scope statement is front-loaded ahead of the accounting tip. Every clause earns its place.

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 an 8-parameter, all-optional list endpoint with no output schema, the description gives the resource scope and a key field-level hint. It stops short of mentioning pagination or the shape of a result, which an agent would have to infer from the schema.

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 schema carries the parameter burden and the baseline is 3. The description earns a point above baseline by explaining the relationship between the `type` filter and the `reporting_category` output field, telling the agent which is more useful for accounting grouping.

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?

States a specific verb (List) and resource (balance transactions) and enumerates what those movements are: charges, refunds, fees and payouts. This scope is precise enough to separate it from stripe_balance_retrieve (totals) and from the narrower list endpoints like stripe_payouts_list or stripe_charges_list.

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 accounting framing ('for accounting, reporting_category groups them better than type') implies the reconciliation use case, but there is no explicit when-to-use or when-not-to-use guidance and no routing to alternative list endpoints such as stripe_payouts_list or stripe_charges_list. Usage is inferable, not stated.

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