stripe_list_payouts

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

No annotations are provided, and the description does not disclose behavioral traits such as whether the operation is read-only, pagination behavior, rate limits, or auth requirements. The routing info is present but does not cover safety or side effects.

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 short and free of fluff, but it is not well-structured. It front-loads the operation name and routing info, but the single sentence about arguments is minimal. It is adequate but not efficient in conveying key information.

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?

Given the complexity of Stripe connectors and the presence of many sibling tools, the description is incomplete. It does not explain how to construct the arguments JSON, what the response format is, or any operational details beyond routing. The output schema exists but is not described.

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 only parameter is a generic 'arguments' JSON string. The description says it contains arguments for the connector operation, but does not explain what keys (e.g., limit, starting_after) are valid or expected. With 0% schema coverage, the description fails to compensate adequately.

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 states it is a Stripe connector operation for listing payouts, which is clear enough from the name and the phrase 'operation list_payouts'. However, it does not explicitly define what a payout is or elaborate on the scope, making it somewhat vague but not a tautology.

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 like stripe_list_invoices or square_list_payouts. The description lacks any context about prerequisites, appropriate scenarios, or exclusions.

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