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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description usefully adds that common events are auto-decoded and that the tool is EVM-restricted, but says nothing about scan limits, rate limits, or how undecoded events are returned.

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 sentences, zero filler, with the core action front-loaded and the scope restriction last. Every clause carries information an agent can use.

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 an output schema present, return values need no explanation, and all three parameters are fully documented in the schema. The description covers scope, decoding, and chain restriction, leaving only minor gaps such as pagination or handling of non-standard events.

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% and the chain enum and blocks bounds are fully documented in the schema, so the baseline 3 applies. The description's 'recent' hints at the blocks window and 'any smart contract' reinforces the address parameter, but adds no syntax or format detail beyond the schema.

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 ('Read recent event logs from any smart contract') and adds the capability of auto-decoding Transfer/Approval/Swap events plus the EVM-only scope. It does not, however, distinguish itself from nearby siblings like security.contract.scan, security.contract.verify, or analyze.tx_decode, so an agent must infer the boundary.

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?

'EVM only' is a stated constraint and the chain enum reinforces it, which implies when the tool is applicable. However, there is no explicit when-to-use guidance versus alternatives such as analyze.tx_decode or security.contract.scan, and no exclusions beyond the chain restriction.

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