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

Annotations already declare readOnlyHint=true and destructiveHint=false, but the description adds real value beyond them: the meaning of each status (PAID, CREDITED, DUE, VOID), the fact that some invoices were settled with credits, the required billing:read permission, and the account/MCP key prerequisite. It does not mention pagination or ordering of results.

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?

One dense sentence with the resource and status taxonomy front-loaded, followed by the read-only and permission caveats. The nested parentheticals make it slightly cluttered, but every clause carries information an agent needs.

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?

With no output schema, the description compensates by naming the fields returned (status, due date, overdue flag) and explaining the status enum values. Combined with the permission and account requirements, an agent has everything needed to call and interpret this tool.

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 tool takes zero parameters, so there is nothing for the description to disambiguate. Baseline of 4 applies since no parameter documentation burden exists.

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 the resource precisely (invoices of the account) and defines both categories it covers: monthly usage statements paid with credits and invoices still to pay. It does not explicitly differentiate itself from the sibling gpucloud_get_invoice, relying on the reader to infer list-versus-single.

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?

It establishes the read-only context and notes that payment happens in the console, which implicitly tells the agent this tool is for viewing only. However, it never states when to reach for this tool versus gpucloud_get_invoice or gpucloud_list_transactions, so usage is implied rather than directed.

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