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

No annotations are provided, so the description carries the full burden. It discloses the cost ('$0.09 via x402') and labels the operation as a 'pre-send read', implying no side effects. It lacks details on output format, error behavior, or rate limits. The mention of 'read' and cost adds some transparency, but it's not comprehensive.

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 and packs essential info into two sentences, but the structure is slightly awkward: leading with the cost ('$0.09 via x402:') before the purpose, and the 'Pass to' phrase is cryptic. Still, every piece contributes and it's appropriately short.

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?

For a tool with no output schema and no annotations, the description covers purpose, use case, cost, and basic invocation. It does not describe what the return value looks like (e.g., gas units in wei) or any edge cases. Given the tool's moderate complexity, this is adequate but leaves gaps.

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 67%, with descriptions for to, data, chain, and value but not from or x_payment. The description adds 'Pass to (+ optional from/value/data)', clarifying to as required and listing the main optional parameters, but it omits chain and x_payment. It does not provide extra meaning for the undocumented parameters, though the cost note hints at x_payment's role.

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 estimates gas usage for a transaction via eth_estimateGas across 6 chains. It uses a specific verb ('estimate'), resource ('gas a transaction will use'), and distinguishes from sibling tools like chain_gas_price or chain_transaction_status by focusing on pre-send estimation. The method name and chain scope are explicit.

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 gives clear context: it is the 'pre-send read tx-building, trading and settlement agents make to size gas and avoid out-of-gas reverts.' This implies when to use it (before sending a transaction) and that it is a read operation. However, it does not explicitly name alternatives or say when not to use it, though the context effectively differentiates it from sibling chain tools.

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