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

Beyond the annotations (readOnly, idempotent, openWorld, non-destructive) the description discloses that signature-database matches are unverified hints, gives a latency range (0.2-1 s), states pricing, rate-limit pooling across three tools, and warns that returned page text and on-chain strings are untrusted data. That is unusually rich behavioral context that annotations cannot convey.

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 core purpose and inputs are front-loaded in the first clause, and every sentence carries operational information (mode behavior, latency, price, quota, untrusted-data warning). It is dense and slightly run-on with pricing/quota clauses, but nothing is wasted.

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 still sketches the return behavior ('every candidate that decodes cleanly is returned') and adds quota and security caveats. It stops short of describing the actual response shape or how candidates are ordered, which is the one meaningful remaining gap.

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 already 100%, so the baseline is 3. The description adds genuine meaning by explaining what a null/omitted signature triggers (selector lookup with multiple candidate decodings) and by flagging 0x hex format, which is behavior the schema alone does not imply.

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 states a specific verb + resource ('decode EVM transaction calldata') with the chainpeek prefix, so an agent immediately knows what it does. It does not, however, differentiate itself from nearby siblings such as decode_tx_logs or get_transaction, so the highest band is not quite reached.

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?

It clearly explains the two operating modes: supply an optional signature, or omit it and let the selector be looked up with all cleanly-decoding candidates returned. That is real usage context, but it offers no explicit when-to-use / when-not-to-use guidance relative to sibling decoding or lookup tools.

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