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

Beyond the annotations, it discloses revert behavior (422 with reason, uncharged), pricing model ($0.01/call, first 25 free, failed calls free), and that each call is charged so repeats are not free — which explains the idempotentHint=false. It also confirms the read-only nature, consistent with readOnlyHint=true.

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 the core action and output before usage, semantics, pricing, and the caveat. It is dense but each sentence carries information; the pricing/charge sentence is a bit long but earns its place by explaining non-idempotency.

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?

There is no output schema, but the description enumerates the return values (gas units, gwei, xDAI) and error behavior (422 with reason), and the safety profile is covered by annotations. An agent has everything needed to call it 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 coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema: value is specified in xDAI, calldata is for contract calls, and 'from' matters when the call depends on the sender. This goes slightly beyond the schema's own wording.

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 (estimate) plus resource (gas for a transaction) on a named chain, and specifies the outputs (gas units, gwei, xDAI). It also disambiguates from the sibling gnosis_gas, so an agent can pick it without opening either schema.

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?

Explicitly says when to use it ('before sending a transaction or to price a batch') and names the alternative for the other case ('for the gas price alone use gnosis_gas'). Nothing is left to inference.

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