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

Beyond the annotations it discloses pricing ($0.01/call, 25 free, failed calls free), a 100-log result cap, the 1-1,000 block scan window with default 50, and warns that repeats are charged so retries are not free — consistent with idempotentHint=false. This is exactly the kind of cost and limit context annotations cannot carry.

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 the core semantics, then returns, then usage, then billing — a sensible order. The billing sentence is long, but every clause (price, free tier, failed-call handling, no-free-retries) affects agent behavior rather than padding.

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?

There is no output schema, yet the description names the returned fields (block, transaction hash, topics) and the row cap. Combined with the block-range limits and cost model, an agent has everything needed to call it correctly and predict the shape of the result.

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 already 100%, so the baseline is 3; the description still adds value by spelling out that topic0 is the 0x 32-byte event signature hash and by giving a concrete example address. It does not expand on block-range edge behavior beyond what the schema states.

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 Berachain (eth_getLogs)') and pins the mechanism to a block window plus optional topic0 filter. It is clearly distinguishable from bera_receipt, which it names, and from the many other bera_* tools.

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 positive use case ('watch transfers or contract events') and an explicit alternative for a specific scenario ('for one transaction's outcome use bera_receipt'). It does not route to bera_token_transfers, which is arguably the better sibling for transfer-watching, so guidance is strong but not airtight.

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