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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered structurally. The description still adds real context beyond that: results are raw canonical entries, the ledger is not modified, large state queries should be paginated, and calls are subject to gateway rate limits — a genuine operational constraint the annotations do not convey.

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 core verb and resource, then the parameter guidance, then the sibling disambiguation last — a sensible ordering. It is a dense, semicolon-chained single paragraph, but every clause carries distinct information rather than padding.

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 still characterizes the return (raw canonical ledger-state entries) and covers pagination, rate limits, and the alternative tool. For a three-parameter read tool with full annotation coverage, nothing an agent needs to invoke 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 100%, so baseline is 3, but the description adds semantics the schema lacks — notably that omitting `ledger_index` falls back to the default ledger, and that `marker` must come from a previous response. That default-behavior and pagination-chaining context goes beyond the field descriptions.

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+resource ("Read-only XRPL raw ledger-state lookup for a ledger") and explicitly distinguishes itself from the nearest sibling, n9t2_xrpl_get_ledger, which is scoped to headers and transaction-list metadata. An agent can route between the two 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?

Gives explicit operational guidance: omit `ledger_index` for the default ledger, supply it to pin a lookup, use `limit` to cap results, and pass `marker` to continue pagination. It also names the alternative tool and the condition that selects it, leaving nothing to inference.

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