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

Annotations already declare readOnly/openWorld/idempotent/non-destructive, so the description adds genuinely new context: the 0.02 USDC per-call cost, the x402 payment rails (Solana, Base, Polygon, Arbitrum, Arc), and data provenance ('read from the chain, summarised by us'). It stops short of rate limits or pagination behavior, keeping it from a 5.

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 two-sentence structure is largely waste-free. The enumeration of return fields is somewhat list-like but each item earns its place by telling the agent what the payload contains.

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 an output schema covering return values and annotations covering the safety profile, the description only needs to add provenance and cost — both present. The main residual gap is that it never contrasts itself with the sibling read tools (get_wallet_holdings, get_sol_token_flow).

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% and both params (wallet base58, limit 1-25 default 10) are fully documented in the schema. The description adds only 'for any address', which does not extend parameter meaning, so the baseline 3 applies.

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 concrete verb+resource ('recent transactions for any address') and enumerates what each result contains (balance changes, fee, failures, programs invoked), so an agent knows exactly what it gets. It doesn't explicitly differentiate from the close sibling get_wallet_holdings, which letter-of-the-spec keeps it just below 5.

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 'recent transactions for any address' and the per-call cost, but there is no explicit when-to-use, when-not-to-use, or named alternative (e.g. get_wallet_holdings for balances vs this for the tx feed). The agent must infer the routing itself.

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