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

No annotations are supplied, so the description carries the full burden, and it does disclose the read-only nature and the pagination mechanism. However, it says nothing about auth/permissions, rate limits, or what a ledger-state entry looks like, leaving real gaps for a raw-data retrieval 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?

A single tight sentence with the core action front-loaded and the pagination note appended; no filler. It is efficient, though its brevity is partly the cause of the missing parameter detail.

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 3-parameter tool with 0% schema coverage, no annotations, and no output schema, the description leaves too much unstated: which ledger is targeted by default, what limit defaults to, and what shape the returned raw entries take.

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%, so the description must compensate for all three parameters. It explains 'marker' as an opaque pagination cursor (useful), but says nothing about 'limit' (default, max) or 'ledger_index' (accepted values like 'current'/'validated' vs integer).

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 and resource ('Read raw XRPL ledger-state objects'), which is clear enough to separate from sibling n9t2_xrpl_ledger (ledger header/metadata). It does not explicitly name or contrast with that sibling, so it stops short of the top band.

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 only usage guidance is the pagination hint ('use marker to paginate through ledger entries'), which is contextual but not a when-to-use rule. Nothing tells the agent when to pick this over n9t2_xrpl_ledger or when the tool is inappropriate.

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