1s_erc20_transfers_live

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

With no annotations, the description carries full transparency burden. It discloses the method (eth_getLogs), return format (decoded events), and warns about large responses. It doesn't mention rate limits or permissions, but the warning adds value.

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?

Four sentences that front-load the purpose, then add filtering, encoding, and warnings. No redundant or irrelevant content; every sentence earns its place.

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?

Given no output schema, the description explains return values (sender, recipient, value) and covers all parameters implicitly. The block range warning compensates for potential performance issues. No gaps remain.

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%, but the description adds meaning: block params are hex-encoded, omission queries latest block, and the warning about small ranges. This goes beyond the schema's type/pattern descriptions.

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 clearly states it queries ERC20 Transfer event logs, a specific verb-resource combination. It distinguishes by mentioning filtering by token or wallet, setting it apart from sibling tools that handle other ERC types or blockchain data.

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 description provides context on when to use (filtering by token/wallet, hex blocks) but doesn't explicitly contrast with alternatives like 1s_events_live. However, the block range warning and default behavior (latest block) give clear usage guidance.

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