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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the description's 'Read-only' sentence is largely redundant. It does add real value beyond the annotations with ordering ('newest first'), per-entry fields ('amount in cents and the balance afterwards') and a scope exclusion (Billstride credits only, not payments), but leaves page size interplay and pagination metadata unstated.

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?

Three tight sentences, front-loaded with what is returned before the usage hint and the scope caveat. The 'Read-only' sentence is the only one that does not earn its place, since annotations already cover it.

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 carries the burden of describing returns and it does so reasonably: entry types, amount in cents, and post-transaction balance. It omits whether a total count or has-more indicator is returned for pagination, a minor gap for a paged read 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?

Schema coverage is 100% and both parameters (page, limit) carry their own descriptions with defaults and maxima, so the schema does the work. The description's 'at most 100 entries per page' merely restates the limit maximum and says nothing about paging through results.

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?

Names a specific verb and resource ('Lists the account's credit ledger') and enumerates the entry types it returns (invoice charges, top-ups, voucher redemptions, refunds). It also draws a hard scope boundary against customer payments on invoices, though it never names the closest sibling get_balance, leaving that differentiation implicit.

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?

Gives concrete use cases ('explain a balance or find what an invoice cost') that tell an agent when this tool is the right pick. It stops short of naming an alternative tool or stating exclusions, so the agent must infer that get_balance is the summary counterpart.

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