abi_codec

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

No annotations are provided, so the description fully shoulders behavioral disclosure. It describes output fields (encoded, mode, values), explains integer representation as decimal strings and address checksumming, and details packed mode behavior.

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 paragraph that is relatively concise but could benefit from bullet points for readability. However, every sentence provides value and is not 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?

The tool has 5 parameters with some optional ones. The description covers all parameters and return values. It lacks error handling details, but given the complexity, it is sufficiently complete for typical use.

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 0%, but the description explains all parameters: action, types (with examples and normalization), values, data, and mode. It adds necessary context beyond the schema's enum values and type hints.

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: ABI-encode values or ABI-decode call/return/log data. It specifies actions (encode/decode), mentions packed mode as encode-only, and gives examples of type strings. This distinguishes it from generic encode/decode siblings.

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?

The description explains when to use encode vs decode and notes that packed mode is encode-only. It doesn't explicitly exclude alternatives, but the detailed context suffices for correct usage.

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