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

Goes well past the annotations: declares the $0.003 USDC x402 cost, that errors are never charged, a 5-second cache window, and that null means source unavailable rather than fabricated. It also enumerates the sub-fields returned (priority-fee tiers, congestion, L1 data fee, deviationPct, safe/finalized lag), which the annotations cannot convey.

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?

Dense but every clause carries information an agent needs (cost model, sources, field inventory, caching, null semantics). Front-loading the price tag before the purpose is defensible for a paid endpoint, though it delays the primary subject by one clause.

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?

With no output schema, the description carries the full return-value burden and does it: it enumerates the three payload groups, the included one-line summary, and the null contract. Nothing an agent needs before calling is missing.

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?

There are zero parameters and the description states "No params.", so nothing is left ambiguous. Baseline 4 applies; no additional parameter meaning is possible or needed here.

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?

The description names the exact composite resource — Base gas tiers, ETH/USD from three sources with median and deviation, and a four-state network status derived from head block age and the sequencer uptime feed — so an agent can distinguish it from base_gas_price, base_block, and crypto_price without opening a 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?

"Bundle for agents that check Base before acting" gives a clear use context and implies this replaces several single-purpose sibling calls. It stops short of naming those siblings or stating exclusions (e.g., when a focused gas-only call is preferable), so it is clear but not routing-complete.

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