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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds the set of chains evaluated, which is useful context, but says nothing about how ranking is computed, whether results are cached/live, or the response shape.

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?

A single well-formed sentence that front-loads the verb and scope with no filler. It is tight and readable, though it devotes its space to listing chains rather than clarifying the ambiguous speed input.

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 annotations covering safety, the main gap is semantic: the speed enum and its effect on results are unexplained, leaving an agent unsure how to pick a value. Chain enumeration is helpful, but the definition is not quite complete for a cost-ranking tool with an opaque enum.

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 coverage is only 50%: bytecode_kb is documented (default 24 KB) but the speed parameter carries no explanation of what slow/standard/fast affects in the cost estimate. The description is silent on both parameters, so it fails to compensate for the coverage gap on the ambiguous enum.

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?

States a specific verb (rank) and resource (chains by deployment cost), and enumerates the compared chains so the agent knows the scope. It doesn't explicitly differentiate from estimate_tx_cost, but 'deploy a contract or program' vs transaction-cost siblings is inferable.

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 when-to-use or when-not-to-use guidance and no mention of the alternatives estimate_tx_cost or gas_now. The only implicit cue is 'given bytecode size', which hints at the input but does not route the agent between this tool and its siblings.

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