rlp_codec

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

Without annotations, description explains encode/decode behavior, accepted data formats (recursive structure with leaves, JSON arrays), and output format. Lacks edge cases but covers essential behavioral traits beyond the schema.

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?

Two sentences, front-loaded with purpose, no extraneous words. Each sentence earns its place by covering the dual functionality and input/output details.

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 two parameters and no output schema, the description covers input formats and output shapes for both actions. Could mention error handling or limitations, but core completeness is strong.

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 has 0% coverage, but description adds full meaning: action enum values with intended behaviors, and data formats for encode (recursive structure) and decode (hex string). Completely compensates for the schema gap.

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?

Description clearly states the tool encodes structured data and decodes hex strings, with specific verbs and resource types. It distinguishes between the two actions and stands out among siblings like abi_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?

Describes when to use encode (structured data) and decode (hex string), but does not explicitly discuss when not to use it or compare to alternatives. Provides clear context for the action parameter.

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