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

With no annotations, the description carries the full burden and does meaningful work: it declares the tool read-only, discloses a paywall ($0.01 USDC on Base, eip155:8453) and the exact payment carrier params._meta["x402/payment"], states a batch ceiling of 25, and gives the concrete HTTP endpoint. Missing are failure modes (what happens when payment is absent/invalid), rate limits, and the shape of a successful response.

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?

A single dense paragraph that front-loads the core capability list before pricing and endpoint details. It is compact with no filler sentences, though the capability enumeration is a shotgun list rather than a crisp statement of what this endpoint alone returns.

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 and no annotations means the description must cover invocation and returns; it covers payment and batching but not which parameter selects which resource or what the response looks like. The schema's per-property route hints ('for /tx', 'for /block', 'for /batch') do part of the job the description omits.

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 80%, so the schema already documents hash, number and addresses with their route hints, and the description's 'Batch up to 25 tokens' only restates the addresses constraint. The description adds no meaning for chain (the only enum) and references a params._meta["x402/payment"] field that does not exist anywhere in the input schema, leaving the payment parameter undescribed.

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 says it reads Base and Ethereum chain data and enumerates resource types (gas, blocks, balances, token metadata, tx status, nonces, verdicts), but that enumeration describes the entire chainread__ family rather than this specific tool. With siblings chainread__gas, chainread__block, chainread__balance, chainread__token, chainread__tx, chainread__nonce, chainread__verdict and chainread__batch all present, an agent cannot tell what 'code' uniquely does or which one to pick.

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?

There is no when-to-use / when-not-to-use guidance and no reference to any sibling tool despite eight closely overlapping chainread siblings. The only routing-adjacent information is pricing and a mention of free /scan and /t/<address> pages, which is commercial detail rather than invocation guidance.

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