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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=false and openWorldHint=true, so the safety profile is covered. The description still adds real value beyond them: a 100-log return cap, the 1-1,000 block scan window, and the per-call cost model (first 25 free, failed calls free, repeats charged — consistent with idempotentHint=false). This is a solid contribution on top of a well-annotated tool.

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 purpose, then return shape, then routing to a sibling, then cost. Dense but every sentence carries information; the pricing tail is slightly bulky but operationally relevant given per-call charges.

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, and the description compensates by stating the return contents (up to 100 logs with block, transaction hash and topics). Combined with the cost model and block-range limits, nothing an agent needs to call this correctly 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 description coverage is 100%, so the schema already documents address, blocks (1-1000, default 50) and topic0. The description mostly restates these; its only marginal additions are the gloss '0x 32-byte event signature hash' and a concrete example address value. Baseline 3 is appropriate.

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 Mantle (eth_getLogs)') plus scope (last N blocks, optional topic0 filter) and explicitly distinguishes itself from mantle_receipt for single-transaction outcomes. An agent can identify this tool without opening the 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 explicit when-to-use guidance ('watch transfers or contract events') and names the alternative it is not for ('for one transaction's outcome use mantle_receipt'). The block-range and topic0 filter hints tell the agent how to narrow a scan rather than fall back to a sibling.

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