abi_encode

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

With no annotations provided, the description must carry the full burden of behavioral disclosure, but it only restates the encoding functionality. It does not specify the output format (e.g., hex string), error behavior, supported Solidity types, or side effects. 'Standard Solidity encoding' adds a small hint but is not sufficient.

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 extremely concise and well-structured, with no wasted words. While it is short and could be seen as under-specified, the length is appropriate for a simple utility tool. It front-loads the key information.

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?

Given the lack of annotations and output schema, the description is incomplete. It does not explain what the encoded output looks like, whether it supports dynamic types, or any special considerations. The schema covers parameters, but the return value and edge cases remain undocumented.

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 already fully documents both parameters with 100% coverage: 'types' is described as 'Array of Solidity types' and 'values' as 'Array of values corresponding to the types'. The description itself adds no additional parameter semantics, so the baseline score of 3 is appropriate.

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 action (ABI encode) and the resource (parameters), with 'standard Solidity encoding' indicating which encoding scheme is used. It doesn't explicitly contrast with sibling tools like encode_call_data or encode_packed, but the name and description are sufficiently clear.

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 encode_call_data, encode_packed, or abi_decode. The description implies usage for encoding parameters but provides no contextual rules or alternative references.

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