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

Annotations cover safety (destructiveHint=false, idempotentHint=true) but the description adds genuinely useful context beyond them: the exact payment cost (0.010000 test USDC on eip155:84532) and the instruction to preserve the private idempotencyKey for retries. This is meaningful for a paid, non-free method and explains why readOnlyHint is false. It does not describe return shape 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?

Three short, front-loaded sentences with no filler; the operation is stated first, then cost, then the key-handling caveat. Efficient, though the first sentence is near-tautological.

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?

For a paid tool with no output schema, the description does cover payment cost and idempotency handling, which are the key operational facts. It falls short on the filter parameters (the substance of eth_getLogs) and gives no sense of the log records returned, so it is adequate but not complete.

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 50%, and the idempotencyKey already carries a detailed schema description. The description adds retry semantics ('reuse only for retries') which is useful, but the entire params object (topics, address, fromBlock/toBlock, blockHash) is undocumented in both the description and schema, leaving the core query parameters opaque.

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 verb ('Read') and resource ('eth_getLogs from Ethereum') plus the chain id, so an agent knows it fetches event logs. However, 'Read eth_getLogs' largely restates the tool name, and it offers no differentiation from the ~20 sibling eth_* read methods (e.g. eth_getBlockReceipts). The eip155:1 qualifier is the only added specificity.

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?

There is no guidance on when to use getLogs versus alternatives like eth_getBlockReceipts or eth_getTransactionReceipt. The only conditional instruction is about retries with idempotencyKey, which is operational rather than usage-routing.

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