stripe_list_invoices

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It does not mention pagination, rate limits, error handling, or the behavior when customer_id is invalid. The description adds no behavioral context beyond the basic listing operation.

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 but the parameter list is incomplete (limit description missing). The main purpose is stated in a single sentence, which is efficient, but the structued parameter documentation is not fully provided, reducing clarity.

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 tool is a simple list with optional filters, and an output schema exists, so return value details are covered. However, the description does not address potential issues like pagination, ordering, or handling of large result sets, which are important for a list endpoint.

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 schema has 0% description coverage, so the description must compensate. It adds value by listing allowed values for 'status' (draft, open, paid, uncollectible, void) but provides no description for 'limit' (missing value) and only repeats the parameter name for 'customer_id'. It adds some meaning but is incomplete.

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 clearly states 'List Stripe invoices, optionally scoped to a customer,' which identifies the specific verb and resource. It distinguishes from sibling tools like stripe_create_invoice or stripe_get_invoice by name, but does not explicitly differentiate from other list tools.

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 (e.g., stripe_get_invoice for a single invoice). There is no mention of prerequisites, when-not-to-use, or alternative tools.

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