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

Annotations only flag readOnlyHint=false, openWorldHint=true, idempotentHint=false and destructiveHint=false; the description supplies the auth models (free with X-API-Key, otherwise x402 at $0.05), the source-data limit (~10 days of Base public RPC history) and the polling requirement. Those are material operational facts an agent cannot get from the annotations alone.

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?

The sentence is front-loaded with the purpose and the follow-up call before the pricing parenthetical, so nothing important is buried. It is still dense with stacked parentheses and a trailing bracketed host tag that add visual noise without changing the call.

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 must convey what a successful start returns — presumably a job handle that ledger_wallet_report consumes — but it only implies this via 'then call ... until done'. For an asynchronous job-start tool, the missing return/identifier detail is a real gap, though the input side is fully covered by the schema.

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% and each parameter is already documented in the input schema, so the description adds no per-parameter meaning beyond it. It only restates the ~10-day history ceiling that the schema itself covers for days/month. Baseline 3 is 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?

Names a specific verb and resource ('Start a report of outgoing USDC from any Base wallet') with an explicit scope ('over the last N days'). It also names the required follow-up tool, ledger_wallet_report, so the agent can separate this job-starter from the reporting call without opening either schema.

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?

The description gives a clear usage sequence — start here, then poll ledger_wallet_report 'until done' — which is exactly the workflow an agent needs. It stops short of saying when not to use this (for example, versus ledger_gateway or a single-shot alternative), so it earns a 4 rather than a 5.

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