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

Adds substantial context beyond annotations: revert behavior (422 with reason, uncharged), pricing model ($0.01/call via x402 USDC or card key, first 25 free, failed calls free), and the non-idempotent charged-per-call caveat that aligns with idempotentHint=false. readOnlyHint is corroborated by 'reads or computes only and changes nothing'. Rich, but the auth/payment mechanics could be slightly sharper about which key path applies.

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?

Front-loads the core purpose and the sibling routing in the first two sentences, then adds failure/pricing notes. Dense but mostly earning its place; the payment/billing sentence is the longest and could be tightened.

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?

No output schema exists, and the description compensates by naming the returned units (gas, gwei, ETH) and the revert error shape. Combined with full schema coverage and annotations, an agent has everything needed to call and interpret it.

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 100%, so baseline is 3, but the description adds real meaning: it explains that value is in ETH and that the sender matters only when the call depends on it, guiding when to supply optional params. Marginal gain over the schema, hence 4 rather than 5.

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+resource — estimating gas for a transaction on Scroll — and specifies the returned quantities (gas units, gwei, ETH). It explicitly distinguishes itself from the sibling scroll_gas by scoping that tool to the price alone.

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?

Gives explicit when-to-use ('before sending a transaction or to price a batch') and names the alternative plus its selection condition ('for the gas price alone use scroll_gas'). Also tells the agent which inputs to supply for a contract call vs. a plain transfer.

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