stripe_list_balance_transactions

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, and the description does not contradict them. It adds useful operational context about governance routing and states that effect must be read, but it does not disclose return behavior, pagination, rate limits, or other execution characteristics beyond what annotations imply.

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 compact and front-loaded with the tool identity, followed by a readable bullet-list of arguments. The opening line is slightly redundant with the tool name, but each listed argument earns its place by adding semantic context absent from the schema.

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?

The combination of annotations, output schema, and parameter descriptions provides a reasonable baseline for a read-only connector listing tool. Missing context includes what balance transactions represent, how to construct the arguments JSON, and when to select this over other Stripe list tools, which keeps it from being fully 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 description coverage is 0%, so the description must compensate, and it does by explaining each parameter in plain terms: project_id as Authenticated Project UUID, connector_account_ref as Project-bound connector account alias, idempotency_key as stable business-action identity, and approval_ref for resuming a write. The 'arguments' parameter is described only as a JSON string for the connector operation, which leaves the internal shape of the Stripe arguments under-specified but is still meaningful.

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 operation as 'list_balance_transactions' and identifies it as a Stripe connector operation, which is a clear verb+resource pairing. It does not describe what balance transactions are or explain the operation's outcome beyond the name, so it relies on the tool name for full clarity.

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?

No guidance is provided on when to use this tool versus alternatives such as stripe_list_charges, stripe_list_payouts, or stripe_list_invoices. The routing note ('Routes only through the exact project/account governed connector authority') gives some context about authorization, but it does not help an agent choose among relevant Stripe list tools.

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