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

Goes well past the annotations by disclosing the commercial model: $0.01/call via x402 USDC or card key, first 25 free, failed calls free, and 'each call is charged, so repeats are not free' — which explains the idempotentHint=false implication. It also restates the safety profile ('reads or computes only and changes nothing') in plain terms.

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-loaded with what it returns, then usage routing, then pricing. Dense but nearly every clause carries decision-relevant information; the billing sentence is long and could be tightened, but it earns its space given the per-call cost.

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, yet the description specifies the return payload (gas price, base fee, priority fee in gwei, transfer cost), the cost model, and the safety profile — everything an agent needs to call it and interpret the result.

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% and the single optional `only` parameter is fully documented in the schema, so the baseline is 3. The description says 'Takes no input', which mildly understates the presence of the optional `only` filter and adds no meaning beyond the schema.

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 ('Current gas price on Gnosis (eth_gasPrice)') and enumerates the returned fields: gas price, base fee, suggested priority fee, plus the 21,000-gas xDAI transfer cost. It also explicitly distinguishes itself from gnosis_gas_history and gnosis_receipt, so an agent can pick it out of a very large sibling set.

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 decide whether to wait') and a named alternative with its selection condition ('for the fee a past transaction actually paid use gnosis_receipt'). No inference required.

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