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

Annotations already declare readOnlyHint and destructiveHint, but the description adds value beyond them: the price model ($0.01/call via x402 USDC or card key, first 25 free, failed calls free) and the warning that repeats are not free, which is meaningful given idempotentHint=false. It also states 'reads or computes only and changes nothing', confirming side-effect freedom in plain language.

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 purpose and return fields, then usage, then cost, then safety. Mostly earned content, though the pricing sentence is dense and could be tightened; the 'Takes no input' clause is wasted words that also introduce an error.

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, so the description appropriately names the returned values and their units (gwei), giving an agent enough to interpret results. The one gap is the unmentioned 'only' parameter, which is covered by a rich schema description, so the omission is minor.

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?

The schema documents the single optional 'only' parameter at 100% coverage, which would normally set a baseline of 3. However, the description asserts 'Takes no input', which actively contradicts the existence of that parameter and could lead an agent to miss the response-trimming option. Misleading is worse than silent.

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 pair ('Current gas price on Linea') and enumerates the concrete outputs: gas price, base fee, suggested priority fee in gwei, plus the cost of a 21,000-gas ETH transfer. It distinguishes itself from the sibling linea_receipt by scope (current vs. what a past transaction paid).

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 names the alternative for the adjacent question ('for the fee a past transaction actually paid use linea_receipt'). The routing decision is fully determined without opening siblings.

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