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

Beyond the read-only/idempotent annotations it discloses result shape and caps (200 logs, 1 kB data), exact-integer formatting, charging behavior for not_found (200, charged) vs. malformed node answers (5xx, uncharged), expected latency, price, free quota pool, and an untrusted-data warning. This is unusually rich behavioral context.

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?

Dense but front-loaded: inputs, outputs, decoding scope, then caveats and pricing. Every sentence carries information, though the repeated 'chainpeek:' prefix and the long event-family enumeration make it longer than it needs to be.

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 fully compensates by describing the return payload fields, the event coverage, and the error/charging semantics. An agent has everything needed to call it and interpret 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 description coverage is 100% and both parameters are documented there, so the description's restatement of 'chain' and 'hash' adds no new semantics. The one marginal addition is the enumerated chain values, which the schema already carries as an enum.

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?

It names a specific verb+resource ('decode a transaction's event logs') and a narrow scope (Ethereum or Base, specific event families), which is unambiguous. It never contrasts itself with the close sibling get_transaction or decode_calldata, so the agent must infer why this differs, keeping it short of a 5.

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?

Usage is implied rather than stated: use it when you have a tx hash and need decoded logs. It adds a genuine caution ('events are decoded by signature only... check the emitting address') but never names an alternative tool or a when-not-to-use condition.

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