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

With no annotations, the description carries the full burden and does well on the hard parts: it declares read-only scope, states the price ($0.01 USDC on Base, eip155:8453), names the x402 payment field (params._meta["x402/payment"]), states the batch cap of 25, and lists which endpoints are free. It omits failure modes, rate limits, and what a successful response looks like, but the payment/auth disclosure is well beyond the norm.

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?

The text is dense and front-loaded with a capability list, then pricing, then the HTTP endpoint, and every sentence is informative in isolation. However, it is a catalog blurb copied across the whole family rather than a description of this tool, so its length is spent on capabilities the caller won't get from this one endpoint.

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?

For a five-parameter tool with zero required parameters and no output schema, the description should say what the gas call returns and which parameter selects the gas sub-resource. Instead it explains the service and its pricing, leaving the actual invocation — presumably 'chain' plus some implicit mode — undocumented anywhere.

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 description coverage is 80%, so the schema already explains hash, number, address, and addresses. The description adds only one marginal detail — a 25-address batch ceiling — and never maps parameters to the gas operation or explains why 'chain' is an enum of base/ethereum. Baseline 3 fits, but nothing here disambiguates the five optional, none-required parameters.

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 tool is named 'gas' but the description enumerates an entire service's surface — gas, blocks, balances, token metadata, tx status, nonces, verdicts — without saying what this specific endpoint returns. An agent cannot tell from this text whether calling chainread__gas yields a gas price, a block, or a batch of token safety scores; the sibling list (chainread__block, chainread__tx, chainread__balance, chainread__token, chainread__nonce, chainread__batch, chainread__verdict) makes the overlap actively confusing.

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?

No when-to-use guidance is given relative to the nine chainread siblings that each cover one of the listed capabilities. The only routing hint is incidental (free /scan and /t/<address> pages, batch up to 25), which does not tell the agent when to pick gas over block, tx, or nonce.

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