abi_decode

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

No annotations are provided, so the description carries the full burden for behavioral disclosure. It only says 'decode', which implies a pure transformation, but it does not disclose that this is a read-only operation, that it may revert on invalid data, or that it returns a list of decoded values matching the provided types. This lack of detail prevents the agent from anticipating errors or side effects.

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 a single, succinct sentence that starts with the verb 'decode' and clearly states the input and output. It is appropriately brief for a simple tool, though it could include a bit more context without becoming verbose.

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?

This is a low-complexity tool with two required parameters and no output schema. The description and schema together provide enough to understand its basic function, but the lack of usage guidance and details about return values or error handling leaves the description incomplete for an agent that needs to select it correctly among many related utilities.

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?

The input schema covers both parameters (types and data) with descriptions, and schema coverage is 100%, so the baseline is 3. The description adds no additional meaning, but the schema already provides sufficient detail for the agent to understand the parameters.

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 'ABI decode encoded data back to values' clearly states the tool's function: decoding ABI-encoded data into human-readable values. The verb 'decode' and resource 'encoded data' are specific. It distinguishes from sibling tools like abi_encode, which performs the inverse operation, though it does not explicitly name alternatives.

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?

There is no guidance on when to use this tool versus alternatives such as decode_transaction_data or encode_call_data. The description does not mention typical use cases, prerequisites, or when not to use it. This leaves the agent without context to decide between similar tools.

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