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

Goes well beyond the annotations by disclosing the billing model (price per call, x402 USDC or card key, first 25 free, failed calls free) and that repeated calls are charged — which explains the non-obvious idempotentHint=false. It also states 'reads or computes only and changes nothing,' reinforcing readOnlyHint. Not a 5 only because it doesn't mention latency or rate limits beyond the free tier.

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 payload, then usage, then pricing; each clause is informative. It runs long, and the billing/credits detail is dense for a description field, but no sentence is pure filler.

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, and the description compensates by naming every returned field, including the percentile priority fees and window aggregates. Combined with the safety and cost disclosures, an agent has everything needed to call it and interpret the response.

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 schema description already says 'How many recent blocks, 5-100 (default 20)', which the description merely repeats along with an example of blocks=20. No additional meaning about what the window controls in the returned data is added 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 and resource — gas price history on Berachain via eth_feeHistory — and enumerates exactly what is returned: base fee per block, block fullness, 10th/50th/90th percentile priority fees, and low/average/high base fee. It explicitly contrasts with the sibling bera_gas for the current price alone, so the agent can route 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?

Gives three concrete decision contexts (judge whether fees are rising, pick a priority fee, time a transaction) and names the alternative bera_gas with the condition that selects it. The default and valid range for the window are also restated inline, leaving nothing to inference.

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