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

Annotations already declare readOnly and non-destructive, so the bar is lower, yet the description adds real semantics: what an empty gas balance implies, that 'unrecognised' means unsolicited transfers, and which wallet Solana swaps execute from. It omits freshness/caching and payload size expectations for a wallet spread across every chain.

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-loads what the tool returns, then adds conditional rules. Dense but every sentence carries an operational constraint; only the phrasing around 'sellAmount' and the Solana clause is slightly tangled.

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 describe return values — and it does, down to per-chain gas coin, token amounts, USD pricing where available, and the special `solana` sub-object. For a zero-parameter read tool this leaves nothing an agent needs missing.

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?

The tool takes zero parameters, so the baseline is 4; the description correctly reflects a no-argument read and adds no misleading input expectations.

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 ('The connected wallet') and enumerates exactly what is returned: X handle, gas coin, each token with raw amount and USD value. This is clearly distinguishable from siblings like list_chains or search_tokens, which serve different lookups.

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 concrete decision rules for interpreting the result: a chain with no gas coin means use gasless=true or fund it first, and 'unrecognised' tokens must never be counted as money or suggested for sale. It also ties `solana` to the agent wallet that execute_swap trades from. It does not explicitly say when to call this versus a quote/swap tool, but the interpretive guidance is unusually strong.

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