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

Annotations already cover read-only/non-destructive, but the description adds genuinely new context: malformed addresses return 400 with no charge, failed calls are free, results are capped at 50 newest-first, and repeat calls are billed (explaining the non-idempotent hint). Pricing detail is useful but partly promotional rather than behavioral.

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 scope and return shape, then usage routing, then edge cases. Dense but nearly every clause earns its place; the price/free-tier sentence is the one part that runs long relative to its decision value.

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 compensates by enumerating returned fields (direction, counterparty, amount, transaction), ordering, and the 50-row cap. Combined with error behavior and the balance sibling reference, an agent has everything needed to call it correctly.

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 three parameters; the description adds a concrete address example, restates the block window/default, and clarifies that token defaults to USDC. That is modest value on top of a complete schema.

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 (List) and resource (a wallet's recent ERC-20 transfers) plus chain, default token, direction, and result shape. It is immediately distinguishable from ink_token_balance and ink_token_info by naming the exact scope and default.

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 the concrete use case (confirm a payment arrived, see what was sent) and explicitly routes balance questions to ink_token_balance. That is an explicit when-to-use plus named alternative, leaving little to inference.

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