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

With no annotations, the description carries full burden. It discloses read-only behavior (queries logs), pricing ($0.05/call via x402), block span cap, and that unknown signature topics are returned raw. However, it does not mention retry behavior, error handling, or rate limits.

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 repetitive (e.g., nearly identical opening sentences), includes pricing in the middle of the function description, and is overly long. Could be trimmed to one clear paragraph.

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?

Covers main features (supported events, filtering, block range, pricing) but lacks details about the output format (structure of decoded events, pagination, or how to handle raw topics). Since there is no output schema, more guidance on return values is needed.

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 has 100% coverage, baseline 3. Description adds context: lists example event names, explains the relationship between from_block, to_block, and lookback, and gives default values. This adds meaning beyond the schema's terse 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 decoded on-chain event logs from a contract on Base, filtering by event name/signature/block range, and explicitly lists supported event types. It distinguishes from sibling blockchain tools (e.g., crypto_token_dossier) by focusing on raw event logs rather than token metadata or safety.

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?

Implied usage is for querying on-chain events, but no explicit guidance on when to use this tool versus related tools like crypto_wallet_xray or solana_token_safety. No exclusion criteria or alternatives mentioned.

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