eth_tx_codec

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

With no annotations, the description carries full disclosure burden. It clearly states that encode does not sign, decode recovers the 'from' address, and specifies number formats and address checksumming. It does not explicitly declare non-destructiveness or statelessness, but the codec nature implies read-only behavior. Additional details about type inference add transparency.

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 concise with two substantive paragraphs and a concrete example. Every sentence contributes useful information; there is no redundancy or filler. The example illustrates typical usage, aiding understanding without unnecessary length.

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 output schema and complexity (two actions, field inference, multiple formats), the description provides complete coverage. It explains both actions, return formats for each ({type, raw, hash} for encode, {type, fields, hash, from} for decode), and includes an example. No gaps are apparent.

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?

Despite 100% schema coverage, the description adds significant semantic value beyond the schema. It explains how to structure the 'fields' object for encode, the inference rules for transaction type, accepted number formats (int/decimal/0x-hex), and that 'data' is required for decode. This enriches the schema's basic parameter descriptions.

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: 'Serialize signed tx fields into a raw transaction, or decode a raw tx.' It specifies the two actions (encode/decode) and the resources involved, making it distinct from sibling tools that handle other codec tasks (e.g., abi_codec, rlp_codec).

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 how to use the tool with action=encode or decode and the required parameters. However, it does not explicitly state when to use this tool over alternatives like rlp_codec or abi_codec, nor does it provide contraindications. The usage context is implied for Ethereum transactions but lacks direct comparison.

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