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

Well beyond what readOnlyHint/openWorldHint convey: it discloses the upstream source (public Linea RPC), an explicit data limitation (batch/proof IDs are not exposed by the RPC and are not reported), and the payment/failure model ($0.002 USDC per successful call via x402 on Base/Solana/Arc; failed calls are not charged). That pricing and non-billing-on-failure detail is directly decision-relevant.

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 resource and metric list, followed by the limitation and pricing caveats — a sensible order. The metric enumeration is dense in one long sentence but every clause names a distinct returned field, so little is wasted.

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?

An output schema exists, so return-value explanation is unnecessary; the description covers source, scope, known blind spot, and cost. Only rate limits or freshness/latency expectations for the RPC data are absent, which is minor for a read-only snapshot tool.

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 tool takes zero parameters, so the baseline is 4. The description correctly implies a single unfiltered snapshot and adds no spurious parameter discussion, leaving nothing for the schema to conflict with.

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 a specific verb/resource pair — Linea zkEVM rollup telemetry from the public Linea RPC — and enumerates exactly which values it returns (latest/safe/finalized blocks, finality lag, gas price, base fee, gas used %, average block time). This clearly separates it from generic L2 or gas tools in the sibling list, though it never names an alternative explicitly.

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?

Usefulness for Linea-specific finality and gas telemetry is implied by the enumerated metrics, but there is no statement of when to prefer this over crypto_arbiscan_l2_rollup, crypto_scroll_l2_zk_proofs, or crypto_ethereum_gas_telemetry. The agent must infer the boundary, which for a zero-parameter tool is a real gap since nothing forces dispatch to this tool specifically.

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