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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuine behavioral context beyond them: history depth depends on the serving node and older pages may be slower, which matters for an agent deciding whether to paginate deeply.

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-loads purpose, then routes usage with labeled clauses, and closes with an example. Mostly tight, though the archival-history caveat is squeezed into the 'Prefer another tool' sentence rather than standing on its own.

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 an output schema present (return values need not be explained) and annotations covering safety, the description supplies the missing pieces: when to use it, when to use something else, and node-dependent history depth. Nothing needed to call it correctly is absent.

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% – address, limit (1-50, default 20) and marker are all documented in the schema. The description only adds a concrete example invocation, which illustrates but does not extend parameter semantics. 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?

States a specific verb and resource ('One page of an account's most recent validated transactions, newest first') including scope (one page, validated, newest first). This clearly separates it from siblings like xrpl_account_summary and xrpl_account_lines.

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?

Explicit 'When to use' clause enumerates the scenarios (payments, offers, trust line changes, success status), then a 'Prefer another tool' clause names the exact alternatives (/summary, /lines) and conditions that select them, plus guidance for archival history.

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