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

Annotations already establish readOnly and openWorld, and the description adds genuinely new behavioral context the annotations cannot carry: the tool decodes rather than returns raw data, the cost of $0.005 USDC per call via x402, and the shape of what comes back (amounts in/out, counterparties, fees, explorer links). It stops short of explaining rate limits, pagination, or what happens on an invalid address.

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-loaded with the core capability, then the return content, then the filter and the price. Three tight sentences 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?

With no output schema, the description properly compensates by enumerating the returned fields, and it discloses the x402 cost. Minor gaps remain around pagination/limit semantics and any prerequisite for paying per call.

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 all three parameters are already documented. The list of decoded categories (swaps, transfers, NFT sales and mints, staking) loosely maps to the `type` filter values and adds a little meaning, but `limit` behavior and type syntax beyond the schema enum are not elaborated.

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: decoding a Solana wallet's recent transactions into readable descriptions, with an enumerated list of what is decoded (swaps, transfers, NFT sales/mints, staking). It is clearly distinguishable from generic siblings like wallet or tx_explain, but it never explicitly names which sibling to prefer.

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?

'Filter by type' is the only usage hint, and it describes a parameter rather than a use case. There is no explicit statement of when to call this versus solana_wallet, wallet_portfolio, tx_explain, or wallet_watch, so context must be inferred.

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