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

Annotations only declare readOnlyHint=true; the description adds substantially more – an unusual two-step payment requirement, the exact retry location for the signed payment, and the fact that results can be marked "truncated": true. That truncation flag is important behavioral context an agent would otherwise miss. It stops short of disclosing limits, result caps, or pagination strategy.

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 purpose and parameters are front-loaded, but the description then embeds a large raw JSON sample containing two full log objects, which is bulky relative to the information it conveys. The verbatim parameter recap duplicates the schema. Usable, but it could be meaningfully tightened.

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 measured output sample legitimately fills a real gap by showing the return shape (count, from_block, to_block, truncated, logs array fields). Payment behavior is fully explained. The notable omission is sibling differentiation, especially against eth_mainnet_logs_and_tx, which an agent must resolve elsewhere.

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%, and the description essentially restates the schema verbatim (address 0x+40 hex, topic0 optional 0x+64 hex, blocks 1-100 default 10), adding no semantics beyond it. This is the baseline case where the structured schema carries the parameter burden.

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 – reading a contract's event logs on Ethereum mainnet, filtered by topic and block range – and names the underlying JSON-RPC method (eth_getLogs). However, it never distinguishes itself from closely related siblings such as eth_mainnet_logs_and_tx or the Base/Gnosis eth_getlogs variants, so an agent must infer which one to pick.

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 gives a clear invocation protocol for the x402 payment handshake (call once with no payment, then retry with the signed payment at _meta["x402/payment"]), which is genuinely actionable. But it offers no guidance on when this tool is preferable to sibling log/transaction tools, and no exclusions or prerequisites for the query itself.

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