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

Beyond the annotations, the description discloses substantial behavioral context: per-rail outputs, XRPL reserve/fee/trust line handling, no USD valuation, no risk score, public RPC usage, nothing stored, charging behavior on bad input or RPC failure, untrusted third-party content, per-call pricing, and payment terms. This is exactly the kind of context an agent needs before invoking a paid external read.

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?

The description is front-loaded and information-dense, with no filler sentences. It is somewhat run-on and mixes tool behavior, pricing, payment rails, and legal terms in one paragraph, but nearly every clause adds actionable context.

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 complex paid balance-checking tool with no output schema, the description covers the rails, per-rail returned fields, limitations (no risk score, no USD valuation), error charging caveats, trust warning, and payment mechanics. An agent has enough information to invoke it correctly and interpret the results.

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 parameter descriptions already document evm, xrpl, and solana. The description repeats 'GET at least one of evm (Base+Polygon), solana, xrpl' and adds little parameter-level meaning beyond the schema; baseline 3 is appropriate when the schema does the heavy lifting.

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?

The description states a specific verb and resource: 'Wallet balance API for x402 payers', listing supported stablecoins and chains. It distinguishes the tool's scope from generic portfolio or funding tools by specifying per-rail payer balances, gas/fees, canPay status, and call capacity, and by explicitly excluding risk scoring and USD valuation.

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?

Usage is implied by 'for x402 payers' and the instruction to supply at least one of evm, solana, or xrpl. However, it does not explicitly say when to use this tool versus siblings like portfolio, funding, or x402_check, nor does it state when not to use it.

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