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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is fully carried by structured data and the description's 'read-only' restates it. The description does add genuine context — 'canonical' (validated-ledger) scope and the catch-all role — plus pagination via limit/marker, but it says nothing about the shape of returned ledger entries or error behavior. With annotations doing the heavy lifting, a 3 is appropriate.

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 capability, then the routing rules, then parameter tips — a sensible order with no filler. Five dense sentences is on the long side, but each carries distinct information (scope, catch-all role, four alternatives, object_type caveat, pagination).

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 7-parameter read tool with full annotation coverage and no output schema, the description covers what it is, when to prefer it, and how to page and pin the lookup. The only real gap is that the return shape of 'raw ledger-entry objects' is left implicit, which matters because there is no output schema to fall back on.

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 the baseline is 3, but the description goes beyond the schema by explaining the intent behind a parameter choice: set object_type to 'nft_offer' only when raw NFTokenOffer ledger entries are required, and use ledger_index to pin the lookup. That routing rationale is not derivable from the schema text alone.

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 and access mode ('Read-only XRPL canonical ledger-object lookup for one account') and immediately names the four sibling views it supersedes. An agent can distinguish this catch-all from n9t2_xrpl_list_account_nfts, n9t2_xrpl_list_nft_offers, n9t2_xrpl_list_account_offers and n9t2_xrpl_list_account_channels 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?

Gives an explicit selection rule: use this 'low-level catch-all when raw ledger-entry objects are required or when no dedicated N9T2 view exists', then enumerates each alternative and the condition that routes to it (NFTs, marketplace offers on a specific NFTokenID, classic DEX offers, Payment Channels). Both when-to-use and when-not-to-use are covered.

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