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

Annotations cover safety, but the description adds substantial behavior beyond them: public RPCs, nothing stored, no charge on bad input or RPC outage, the XRPL fee non-reservation caveat, per-call price and payment rail (Base-only x402), and an explicit prompt-injection warning about untrusted returned content. That is exactly the extra context annotations cannot express.

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 is front-loaded and the dense clause-per-fact style packs payment terms, failure behavior, and safety caveats efficiently. It is closer to a run-on list than a structured summary, but nearly every sentence carries non-redundant information.

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 carries the return burden well: it enumerates per-rail outputs (USDC/RLUSD balance, gas/fees, XRPL reserve/trust line, canPay, calls left) and covers pricing and error semantics. An agent has what it needs to call and interpret this tool.

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%, so baseline is 3; each parameter is already documented with its rail and what it yields. The description restates the rail mapping (evm = Base+Polygon, xrpl = RLUSD/trust line/reserve) without adding format, validation, or mutual-exclusion detail beyond the schema.

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+question answered: 'x402 payer balance check: can this wallet pay right now.' It also scopes itself against siblings by naming the rails (Base+Polygon, Solana, XRPL) rather than generic balance lookup, so an agent can separate it from gas, portfolio, or x402_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 invocation rule ('GET with at least one of evm, solana, xrpl') and an implied use case (deciding whether a wallet can pay now). It does not explicitly name alternatives such as x402_check or gas, nor state when not to use it, so it stops short of full routing guidance.

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