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

Annotations already cover readOnly/idempotent/non-destructive/closed-world, so the description is not obligated to restate safety. It adds value with the auth requirement and the pagination behavior, plus a clear negative statement that no payment is initiated.

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 short sentences, zero filler, with the core read action and returned data front-loaded before the exclusions and auth note.

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?

An output schema exists, so return shape needn't be explained, and the auth prerequisite is stated. The only real gap is cursor semantics for `before`, which an agent needs to page backwards correctly.

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 description coverage is 0% across two parameters, so the description must carry the meaning. It only says "pagination", which hints that both params are paging controls but never explains that `before` is an opaque `timestamp|id` cursor or that limit defaults to 25 and caps at 100.

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?

States a specific verb and resource — read the workspace credit ledger — and enumerates what the ledger contains (amounts, balances, order references, pagination). It implicitly separates itself from get_credits by framing this as historical ledger reading, though it never names that sibling.

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?

"Does not fund an account or initiate payment" explicitly rules out the write/payment siblings, which is real when-not guidance. What's missing is a positive rule for choosing this over get_credits (current balance) versus this ledger history.

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