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

Annotations cover read-only/open-world, but the description adds substantial context beyond them: the daily free-call rule, the payment rail (x402, USDC on Base, or XRP/RLUSD), billing on the first call for a payment watch, and that bad input or ledger outages are never charged. This is exactly the kind of operational detail an agent cannot derive from structured fields.

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?

Purpose and scope are front-loaded in the first long sentence, followed by when-to-use and pricing. Every sentence carries distinct, non-redundant information with no 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?

For a one-parameter read tool with no output schema, the description covers what is checked and the billing model, which is sufficient to call it correctly. It does not describe the shape of the returned verdict (booleans vs. flags), a minor gap.

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?

Single parameter with 100% schema description coverage, so the schema already documents the r-address fully. The description adds no syntax or format guidance beyond it, making the baseline 3 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 ('Checks whether an XRP Ledger token issuer is who it claims to be') and enumerates the exact checks performed: two-way domain verification, tokens issued/outstanding, and control flags. This is unmistakably distinct from siblings like token_check or payment_check.

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 a clear use context ('Useful before accepting or holding a token') plus the cost/prerequisite model (first call per day free, then ~$0.01 via x402). No alternatives or exclusions are named, so it falls short of a 5.

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