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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false, and destructiveHint=false. The description adds meaningful behavioral context beyond that: it is pure offline computation with nothing fetched or stored, and it itemizes the analytical outputs the agent will receive.

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 first sentence is dense but front-loaded and informative. The second sentence about combining with swapchan_playbook lists unrelated workflows (find-money, best-swap, etc.) and does not directly help invoke bytecode_inspect, making it low-value padding.

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?

With no output schema and only one input parameter, the description carries the burden well by enumerating the classifications and derived data returned. It could be stronger on input constraints like the 59000-character maxLength, but overall it gives an agent enough to call and interpret the tool correctly.

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 description coverage is 0% and there is one required parameter, so the description must compensate. It does by specifying the parameter's expected format as eth_getCode hex, which is the key semantic detail an agent needs beyond the bare string type.

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 uses a specific verb ("Classify") and resource (contract runtime code), and enumerates the exact fields returned (EIP-1167, EIP-7702, EOF, EIP-170 size, keccak, metadata, opcodes, selectors). This makes the tool's function unmistakable, though it does not explicitly contrast itself with sibling inspection tools like contract_reader or evm_abi.

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?

It clarifies the expected input is eth_getCode hex and that the operation is offline, which implies usage context. However, there are no explicit when-to-use/when-not conditions or direct alternatives named; the pointer to swapchan_playbook workflows is tangential rather than a routing rule.

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