stripe_list_charges

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

With no annotations provided, the description must fully convey behavior. It only says 'List recent Stripe charges.' and lists parameters. It does not disclose that this is a read-only operation, whether it returns all charges or paginated, any rate limits, or what constitutes 'recent'. This is insufficient for safe use.

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 very short but includes an incomplete line for limit (just 'limit: ' with no explanation). This suggests a cut-off or error, making it less useful. While conciseness is valued, missing content is not acceptable.

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 tool has 3 parameters, an output schema exists, and no annotations, the description should provide more context about what 'recent' means, whether charges are sorted, and any restrictions. It fails to address these gaps, leaving the agent with incomplete understanding.

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 should add meaning. It provides brief descriptions for customer_id and from_date (e.g., 'Stripe customer ID to filter by', 'Start date (YYYY-MM-DD)') but the limit parameter has an empty description. This incomplete coverage leaves the agent unsure about the limit field's purpose and constraints.

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 'List recent Stripe charges.' which clearly identifies the action (list) and the resource (Stripe charges). It is distinct from sibling stripe tools like stripe_list_invoices and stripe_list_payouts, but 'recent' is vague and could be more specific.

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_balance_transactions or stripe_list_invoices. There is no mention of prerequisites or context that would help the agent decide when to invoke this tool.

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