stripe_list_balance_transactions

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

No annotations are provided, so the description must disclose behavioral traits. It only describes the routing mechanism but does not state that the tool is read-only, whether it returns paginated results, or any side effects. The opaque 'arguments' parameter further obscures behavior.

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 relatively short (three lines) but includes redundant routing information that may not be essential for tool selection. The 'Args' line is minimal. It is adequate but could be more concise by omitting the low-level routing details.

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?

Although an output schema exists (so return values need not be explained), the description lacks key context: what constitutes a balance transaction, how to filter or paginate, and the purpose of the arguments parameter. For a list tool with a single opaque parameter, this is incomplete.

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 input schema has only one parameter 'arguments' as a string with 0% schema description coverage. The description adds 'JSON string of arguments for the connector operation,' which does not specify the expected keys, values, or format. This fails to compensate for the schema gap and provides no meaningful semantics.

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 name 'stripe_list_balance_transactions' clearly indicates it lists balance transactions from Stripe. However, the description merely restates the operation name and doesn't differentiate it from sibling list tools like 'stripe_list_charges' or 'stripe_list_invoices', leaving ambiguity about what a 'balance transaction' specifically entails.

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 provides no guidance on when to use this tool versus alternatives. It only mentions routing scope, which is not usage advice. Without context on prerequisites or comparison to other Stripe list tools, the agent cannot determine when this is the appropriate choice.

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