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

The readOnlyHint annotation already tells the agent this is a safe read, so "READ ONLY — does not post value" is largely redundant; the added clause that it does not post value to the ledger is a small clarification. Nothing is said about pagination behavior, result limits, or ordering beyond what the schema exposes.

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?

Two short clauses, front-loaded with the operation and resource, with no filler. Slightly terse for a list tool but nothing is padded or buried.

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 a zero-required-parameter list tool with full schema coverage and readOnlyHint annotations, the description is minimally sufficient, but with no output schema it gives no hint about the shape of returned ledger transactions or pagination envelope (next_cursor / X-After-Cursor). Adequate but with clear gaps.

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 100% across all three parameters, so the schema already documents per_page limits, ledger_id filtering, and the after_cursor semantics. The description adds no parameter meaning beyond that, making the baseline 3 appropriate.

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 (List) and resource (ledger transactions) plus the underlying endpoint GET /ledger_transactions. It does not distinguish itself from close siblings such as modern_treasury_list_ledger_entries or modern_treasury_list_transactions, so an agent must infer the boundary from the resource noun alone.

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?

No when-to-use guidance, no mention of alternatives (e.g. list_ledger_entries vs list_ledger_transactions), and no prerequisites. The only usage-adjacent statement is the READ ONLY marker, which is restated from the annotations rather than routing the agent between tools.

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