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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds real behavioral context beyond that: pending, ambiguous, and batched-attribution legs are excluded from settled totals, and a checksum is explicitly not proof of authenticity or independent settlement. These caveats materially change how an agent should interpret results.

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 purpose is front-loaded, but the opening sentence is a comma-spliced fragment stack ('partial selected-network public web-dispatch transfer ledger and balanced exact micro-USDC vouchers') that is hard to parse. Density serves the tool's many caveats, yet the phrasing could be tightened without losing any of the disclosed constraints.

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 read-only, single-parameter ledger with no output schema, the description covers the essential gaps: what the ledger contains, what never enters settled totals, what data is deliberately absent, the export endpoint, and the checksum caveat. An agent can call and correctly interpret this tool from the description plus annotations alone.

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% and the single 'days' parameter is undocumented in the schema, so the description must carry it. It supplies the meaningful missing piece — the default of 7 — and reiterates the 1–31 bounds; only the bounds duplicate the schema's min/max, so added value is real but modest for a one-parameter tool.

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 concrete verb-resource pair (inspect a public web-dispatch transfer ledger and micro-USDC vouchers) and scopes it as 'partial' and 'selected-network'. The 'public' qualifier implicitly separates it from the private siblings (history_private_jobs_*, history_private_jobs_detail), though the heavy domain jargon ('balanced exact micro-USDC vouchers', 'sponsorship') blurs the purpose for an outside agent.

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?

Provides a strong when-not boundary by enumerating what the ledger deliberately excludes (customer questions/identities, private invoices, complete business books, margin, cash balance, signing/execution authority), which steers the agent toward the private/job-detail siblings. It also notes browser funding and Keryx sponsorship are separate concerns. It stops short of naming an explicit alternative tool to use instead.

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