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

Annotations already cover read-only/non-destructive/open-world, so the description correctly spends its words elsewhere: a hard cap of 100 returned logs (truncation behavior), a per-call price with the first 25 free and failed calls free, and the fact that repeats are not free, which explains idempotentHint=false in cost terms. The sentence 'Reads or computes only and changes nothing' merely restates the annotations, but the truncation and billing details are genuine additions.

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 core scope and the sibling routing are front-loaded in the first two clauses, and the example address is cheap and useful. The closing pricing sentence is long and partly boilerplate across the tool family, though the 'failed calls free' and 'repeats are not free' details do earn their place.

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 description carries the burden of describing returns and does so ('up to 100 logs with block, transaction hash and topics'), plus limits, pricing and an example. What is missing is ordering/recency semantics and whether the 100-log cap silently truncates a busy contract, which matters for an agent scanning a wide block range.

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 all three parameters are already documented, and the description mostly repeats the block range and default verbatim. It adds modest value by specifying that topic0 is a 32-byte signature hash and by supplying a concrete example address, but it gives no guidance on topic0 formatting variants or on how blocks interacts with the 100-log cap.

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 and resource ('Recent contract event logs on Ethereum (eth_getLogs)'), names the exact parameters that scope it (blocks, topic0), and gives the return shape. The clause 'for one transaction's outcome use eth_receipt' separates it from the nearest sibling without opening a 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 an explicit when-to-use ('watch transfers or contract events') plus one named alternative with the condition that selects it (eth_receipt for a single transaction's outcome). It stops short of a full routing story — eth_token_transfers is the more natural sibling for watching token transfers and is never mentioned, so the transfer advice is slightly underspecified.

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