List ledger transactions

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, so the description does not need to repeat those. The description adds ordering ('most recent first') and a use case, but does not disclose details like pagination behavior or rate limits. Given the annotations cover safety, a score of 3 is appropriate.

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 extremely concise: two sentences that immediately state the action and provide context. Every sentence adds value, and there is no redundancy. It is perfectly front-loaded for an agent to quickly understand.

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's simplicity (one optional parameter, no output schema), the description is mostly complete. It explains what the tool lists and in what order, and gives a usage example. The only minor gap is that the return format is not described, but for a list tool this is often acceptable.

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?

There is a single parameter 'limit' with full schema description coverage. The tool description does not add any additional information about the parameter beyond what is already in the schema. With 100% coverage, the baseline is 3, and no extra value is provided.

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 that the tool lists billing ledger journal entries in reverse chronological order. It includes a concrete example ('why did my balance drop yesterday'), which helps agents understand the purpose. It is easily distinguishable from siblings like bill_get_balance or bill_list_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?

The description provides a usage scenario: tracing payments, charges, and adjustments. It gives an example query ('why did my balance drop yesterday'). However, it does not explicitly mention when not to use this tool or compare it to alternatives, so it slightly lacks exclusion criteria.

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