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

With no annotations, this description carries the full burden and does substantial work: it discloses the per-call cost (1 CRD), that the charge applies even to a later rejection, that a 429 RATE_LIMITED is free, and that errors return a request_id to quote to support. It stops short of describing auth requirements or return record shape, which keeps it from a 5.

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, each front-loaded with a distinct concern: what it returns, how to filter/paginate, and the cost/error contract. Nothing is redundant and even the parenthetical about 429s earns its place as cost-clarifying detail.

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?

For an eight-parameter, zero-required read tool with no output schema, the description covers the operation, filtering, pagination, billing behavior, and error handling contract. The remaining gap is the shape of a returned transaction, which the agent must discover empirically.

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%, so the baseline is 3; the description adds value by framing email and user_id as alternative ways to filter by user and by grouping limit/offset as pagination. It does not clarify the optional project_id or the x402_payment fallback flow beyond what the schema already says.

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 ('List ledger transactions'), adds ordering ('newest first') and enumerates the transaction types (issue, deduct, refund). It is clearly distinct from mutation siblings like deduct_credits or issue_credits, though it never explicitly distinguishes itself from near-neighbors such as list_deposits.

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 practical usage context by naming the available filters (user via email or user_id, credit_type_id) and pagination controls, so an agent knows how to narrow a query. However, it never says when to choose this over list_deposits or get_balance, nor are prerequisites or exclusions stated.

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