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

With no annotations, the description carries the full burden and does well: newest-first ordering, cursor pagination, no auth, chain omitted from rows, unknown chain spellings refused, and chain-selection heuristics (T…/base58 address filter selects Tron/Solana, otherwise Base). It does not define the 'recent' window or any rate/coverage limits, but the disclosed behavior is substantial.

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 purpose and scope, then pagination, then the return shape. Dense but every clause carries information; the trailing output-field enumeration is long, though justified because no output schema exists.

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 usefully enumerates returned fields (tx_hash, block_time, amount in minor units, finality, usd_amount) and states pagination and auth posture. The main gap is that 'recent' has no bounded time window, leaving the coverage horizon ambiguous.

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 the schema already documents all five parameters in depth. The description largely restates schema facts (chain not repeated in rows, default chain behavior) rather than adding new 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?

States a specific verb+resource+scope: 'Recent stablecoin transfers on ONE chain (newest first), filterable by recipient/payer, cursor-paginated.' This is clearly distinguishable from the address-risk/approval/sanctions siblings, which are entity-centric rather than feed-centric.

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?

The 'No auth' note and the filter/pagination framing imply when this is useful, but the description never states when to prefer it over siblings like get_address_exposure or get_wallet_graph_walk, nor any exclusions. Usage is inferable rather than explicit.

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