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

Goes well beyond the annotations by disclosing the pricing model ($0.01/call via x402 USDC or card key, first 25 free, failed calls free), the per-call charge implication for repeats (consistent with idempotentHint=false), and the 100-log result cap. The only redundancy is restating that it changes nothing, which readOnlyHint already covers.

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-loads what it does, the range/default, and the result shape before pricing, so the important routing info comes first. Some content is duplicated across description and schema (block range, topic0 hash format) and across description and annotations (read-only nature).

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 still specifies the return shape (up to 100 logs with block, transaction hash, topics), the scan window and default, and the cost model. Nothing an agent needs in order to decide and invoke is missing.

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 block range, default, and topic0 definition are already documented in the schema; the description largely restates them. The one addition is a concrete example address, which is marginal rather than explanatory.

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 ('recent contract event logs on Celo') and maps it to the underlying RPC call (eth_getLogs), so an agent understands exactly what is fetched. It explicitly positions itself against the sibling celo_receipt for single-transaction outcomes.

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 a clear when-to-use ('watch transfers or contract events') and names the alternative celo_receipt with the condition that selects it. It does not mention the closely overlapping celo_token_transfers sibling, which also returns transfer events, leaving one routing ambiguity.

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