billing_list_invoices

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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It only states that the tool lists invoices and returns pagination info; it does not mention authentication, scope of 'all' (account-wide, project-wide, etc.), allowed statuses, or error behavior. For a billing-sensitive read operation, this is a meaningful gap.

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 tight and well-structured, front-loading the action and then using a clean Args/Returns layout. Every sentence earns its place with no filler or repetition.

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 large sibling set and the existence of confusingly similar billing tools (billing_list_billing_history, billing_get_invoice, billing_list_invoice_items), the description fails to situate this tool among its alternatives. It also leaves pagination mechanics vague (e.g., how a caller obtains subsequent pages), so the agent cannot fully predict how to use the result.

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 provides no description for per_page, so the description's 'Number of items per page (default: 25)' adds the core semantic meaning. However, it largely restates the schema default and does not explain null behavior or any constraints, so it only partially compensates for the 0% schema coverage.

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 a specific verb and resource ('List all invoices') that is immediately understandable. It does not, however, distinguish itself from closely related billing siblings like billing_get_invoice or billing_list_billing_history, so it stops short of full clarity.

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?

There is no guidance on when to use this tool versus billing_list_billing_history, billing_get_invoice, or billing_list_invoice_items. The description gives no context about what distinguishes 'invoices' from other billing artifacts, and it offers no exclusions or alternative routing.

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