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

Annotations only cover readOnly/openWorld; the description goes well beyond them by disclosing the pricing model (first call per day free, ~$0.02 via x402 USDC on Base or XRP/RLUSD on XRPL), that payment watches are charged from the first call, and that bad input or ledger outages are never charged. Those billing and failure-path traits are exactly what an agent needs before invoking a metered tool.

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?

Front-loaded with the resource and its visual semantics, then defaults, then cost. The payment sentences are long but each carries decision-relevant information (free tier, price, non-billable failures); only the 'posts, reports, newsletters' clause is close to filler.

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 correctly specifies the return artifact and its contents, plus defaults and cost. The main remaining gap is the network parameter's effect and whether historical ledger_index values are accepted/validated, but nothing essential to calling it correctly is missing.

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 50% and only the network enum is documented in-schema. The description compensates partly by defining the default ledger_index behavior ('Latest validated ledger by default'), though it says nothing about how network=testnet affects the rendered ledger.

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 artifact (1200x675 PNG of one validated XRP Ledger ledger) and exactly what it depicts: one tile per transaction in ledger order, colored by type, failed transactions hollow. This is distinguishable from sibling tools like ledger_pulse or large_payments without opening any 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?

Provides defaults (latest validated ledger) and an audience ('posts, reports, and newsletters about network activity'), which implies usage, but never states when to choose this over siblings such as ledger_pulse or receipt_card, nor any exclusions.

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