get_invoices

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

No annotations provided. The description implies a read-only listing but does not disclose behavioral traits such as pagination, data freshness, or any limitations on the number of invoices returned. It adds some context by mentioning Stripe as the source but lacks details about side effects or scope.

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?

Two concise sentences that front-load the purpose. No fluff, every word earns its place.

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?

For a simple list tool with no parameters and no output schema, the description covers the key aspects: what it does (list invoices) and what it shows (details). Could optionally mention ordering or date range, but completeness is adequate given the tool's simplicity.

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?

No parameters in the schema, which is expected for a simple list-all tool. The description adds meaning by specifying the source (Stripe) and the type of details shown (amounts, status, dates). Per guidelines, baseline for 0 parameters is 4, and the description meets this 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?

Description clearly states it lists all invoices from Stripe with details like amounts, status, dates. The verb 'List' and resource 'invoices' are specific, and it distinguishes from sibling tools like get_billing_alerts or get_payment_methods by focusing on invoices.

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 on when to use this tool versus alternatives like get_billing_alerts or get_credit_balance. The description does not mention when to use or not use it, nor any prerequisites or exclusions.

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