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

Annotations already cover the safety profile (readOnly, idempotent, openWorld, non-destructive), and the description adds substantial beyond that: the 10000-block range cap, the 500-log result cap with a "truncated": true signal, default block windows, one explorer request per contract when decoding, and a warning that event string values are untrusted.

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 purpose and limits, and every sentence carries information (caps, defaults, topic semantics, decode behavior, trust warning). It is dense and runs long, but no sentence is wasted.

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?

No output schema exists, and the description compensates by explaining the return shape (capped at 500 logs, truncated flag) and the decoding behavior. Combined with the rich parameter semantics, an agent has everything needed to call and interpret this tool.

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 baseline is 3, but the description goes beyond the schema by explaining topic positions (0 = signature, 1-3 = indexed args), that event_signature computes topic 0, and that from_block defaults to to_block minus 1000. That meaningfully enriches several parameters rather than restating them.

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 (event logs in a block range) and names the underlying mechanism (eth_getLogs), which cleanly separates it from the explorer_* and receipt/transaction siblings. An agent can tell exactly what it returns without opening the schema.

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 clear operating context (filter by contract addresses/topics, narrow the range when truncated, defaults for the block window), which is real usage guidance. It does not explicitly name an alternative sibling or a when-not condition, so it falls short of a 5.

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