eth_tx_codec

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

With no annotations, the description fully discloses behavioral traits: the tool does not sign, type inference rules for transaction types, accepted number formats (int/decimal/hex), address recovery from signature, and checksummed output. It also describes return fields for each action. No contradictions.

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 yet comprehensive, front-loaded with the overall purpose followed by clear bullet-like points for each action. Every sentence adds value; no wasted words. The structure guides the agent quickly to the relevant action.

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 complexity of Ethereum transaction encoding/decoding and the lack of output schema, the description is complete. It covers input requirements, output format, type inference, number handling, and address recovery. No important behavior is omitted.

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 0% schema description coverage, the description compensates completely. It explains the 'action' enum, the 'data' parameter for decode, and the 'fields' object for encode in detail, including how transaction type is inferred and number formats. This adds all necessary meaning beyond the bare schema.

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 serializes signed transaction fields or decodes raw transactions. It specifies two distinct actions (encode/decode) and what they produce, making the purpose unambiguous and differentiating it from siblings like general encode/decode.

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 exactly when to use each action: encode for serializing already-signed fields, decode for parsing raw transactions. It also clarifies that encode does not sign, setting appropriate expectations. Although it does not explicitly list alternatives, the context and sibling tool names make the Ethereum-specific usage clear.

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