Decode event logs to typed JSON (paid $0.003)

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

No annotations are present, so the description carries the full burden. It thoroughly discloses payment requirements (x402 challenge, x_payment settlement), ABI resolution behavior (Sourcify/Blockscout + 4byte), and edge-case handling (tuples, arrays, anonymous events, indexed vs non-indexed). This is exceptionally transparent.

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?

The description is dense but front-loaded with the crucial 'PAID' flag. Each sentence adds necessary information: payment, input modes, return details, ABI resolution, and 402 behavior. No filler or repetition.

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 no annotations, so the description must fully explain behavior and return values. It does so: it describes the return fields (name, canonical signature, named/typed args), covers complex ABI cases, explains payment flow, and identifies the ABI resolution path. This is complete for a moderately complex paid tool.

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 baseline is 3. The description adds value by explaining how parameters combine (tx_hash vs address+topics+data), what 'data' means (non-indexed args), and the x_payment flow (omitting returns 402 challenge, supplying settles via X-PAYMENT header). This goes beyond schema descriptions without being redundant.

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?

The description clearly states the tool's purpose: decode EVM event logs into typed JSON. It specifies two input modes (tx_hash or address+topics+data) and what it returns (event name, signature, args), distinguishing it from sibling tools like decode_calldata by explicitly targeting event logs.

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 guidance is clear: it tells you exactly when to pass tx_hash vs address/topics/data, and when abi is optional. It does not explicitly mention alternatives or exclusion cases, but the 'FLAGSHIP' framing and event-log focus imply when to choose it over decode_calldata.

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