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

Annotations already declare read-only, idempotent, non-destructive, and open-world behavior. The description adds meaningful operational context: billed cost per started 1,000 blocks, adaptive chunking, ordered results, raw fallback, and hard limits on blocks, logs, and output size.

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?

The description is dense and front-loaded: cost and purpose appear first, followed by behavioral traits and limits. Every clause carries useful information with no wasted text.

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?

The tool has rich structured context: full schema coverage, annotations, and an output schema. The description adds the key missing operational details such as pricing, supported chains, chunking, fallback, and caps, though it stops short of explicit usage guidance.

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%, so the schema already documents all six parameters. The description reinforces block-range and output limits but does not add much parameter-specific meaning beyond what the schema provides for abi, topics, address, fromBlock, or toBlock.

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 specific verb and resource: retrieve and decode EVM event logs. It also scopes the supported chains and cost model, making it clearly distinct from sibling tools covering bridges, gas, leads, stocks, and payments.

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 the purpose and constraints, but there is no explicit when-to-use or when-not-to-use guidance. It does not name alternative tools or explain which sibling to choose for related EVM decoding tasks.

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