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

With no annotations, the description carries the full burden and does disclose important traits: a bounded result window, newest-first ordering, and a per-call cost ($0.02 USDC on Base via x402). It omits failure behavior (invalid address, unsupported chain) and whether payment is charged on empty results.

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?

Two dense sentences: the first front-loads what the tool returns, the second front-loads the cost constraint. No filler and no repetition of the tool name.

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?

For a 5-parameter read tool with no output schema and no annotations, the description covers return contents, ordering, window bound, and pricing. What is missing is practical invocation detail: no guidance on choosing chain/token combinations or on narrowing an address's history when the window is too small.

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 60% (chain, token, address documented; limit and blocks undocumented). The description only vaguely gestures at the 'blocks' parameter via 'bounded' and adds no format, default, or range meaning beyond the schema, so it neither compensates for nor worsens the gap.

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 ('List recent ERC-20 transfers involving an address') and adds concrete scope details (bounded, newest first) plus the returned fields. It is not confused with wallet_balance or tx_status, but it never explicitly contrasts itself with those siblings.

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?

There is only an implied use case: 'recent' activity lookups. The description gives no explicit when-to-use, when-not-to-use, or pointer to alternatives (e.g. tx_status for a single hash, wallet_balance for holdings), despite three closely related siblings.

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