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

Annotations already cover read-only and open-world behavior, but the description adds real value: live DEX liquidity pricing, value-sorted output, dust and unpriced tokens flagged, and a concrete cost of $0.005 USDC per call via x402 with the endpoint URL. It does not disclose fallback behavior when a token has no liquidity or what the free-trial response looks like.

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?

Payload content is front-loaded in the first clause and the invocation guidance and pricing follow in short sentences. The opening sentence is dense with clauses (pricing source, sorting, dust flags) but every element carries 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?

No output schema exists, so the description must convey the return shape — and it does: per-asset USD values, live DEX pricing source, value-descending sort, and dust/unpriced flags. Combined with the payment model and endpoint, an agent has everything needed to call and interpret 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 types and the optional payment header are already documented in the schema. The description contributes only the "solana, evm, or both" combination guidance and does not clarify the edge case of supplying neither, so it stays at the baseline.

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 with explicit scope: a single call returning a USD-valued portfolio across Solana and Base, enumerating asset classes covered (SOL, SPL/Token-2022, Base ETH, USDC). This clearly distinguishes it from single-chain siblings like solana_token_balances and base_balance without needing their schemas.

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?

"Pass solana, evm, or both" tells the agent how to invoke it for either or both chains, which implicitly covers the aggregation use case. It never explicitly says when to prefer this over solana_token_balances + base_balance, or what happens if neither wallet is passed despite zero required parameters.

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