List ledger transactions

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description still adds real value with the sign convention ("credits to you are positive") and the claim that each entry carries the causing object, but it says nothing about ordering or how deep the history goes.

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?

It is short and the purpose statement leads, which is good. The second sentence crams definition, sign convention and return shape into one dense clause, while pagination and the default/maximum limit of 10/100 get no mention at all, so length is not the problem, allocation is.

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?

There is no output schema, so the description carries the return-value burden and does partially meet it by naming the signed per-balance effect and the source object. But result ordering, the default page size and the fact that cursors are the only way to reach older entries are never stated, leaving an agent without guidance on iterating a potentially long ledger.

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 enum values are documented in the schema, so the baseline would be 3. The description earns a point above baseline by explaining what the two enum filters actually mean in ledger terms ("journal type", "what caused the movement"), which clarifies the type-vs-source distinction that the schema descriptions leave ambiguous.

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 ("List ledger transactions") and goes further by defining what a transaction is: a journal that moved balances, with a signed effect and the originating object. However, it never distinguishes this from the many sibling list_* tools (list_payments, list_transfers, list_settlements, list_settlement_items), so the agent must infer the boundary itself.

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?

One concrete use case is given ("Use it for reconciliation") plus the filtering options, which implies when it fits. There is no when-not guidance and no named alternative, which matters in a toolset where list_settlement_items and get_balance are plausible substitutes for balance-level reconciliation.

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