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

With no annotations provided, the description carries the full burden and does substantial work: it declares the tool read-only, names the two supported chains, states the price ($0.01 USDC on Base eip155:8453), and explains that payment goes in params._meta["x402/payment"]. It stops short of describing what happens on unpaid or failed calls and gives no rate-limit or error behavior.

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 capability list, pricing and payment mechanics are front-loaded and the HTTP endpoint is placed last, which is the right ordering. The first sentence is a long comma-chained list that could be tightened, but almost every clause carries actionable information.

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, zero-required, multi-mode tool with no output schema, an agent still needs to know which parameter selects which operation and whether parameters combine. Pricing and payment are fully covered, but mode selection and failure behavior are not, leaving a real gap for a tool this flexible.

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 most parameters, and the baseline is 3. The description adds one useful constraint — batch up to 25 tokens — that corroborates the addresses array cap, but it doesn't clarify which parameter triggers which sub-resource or whether they are mutually exclusive.

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 lists concrete resources (gas, blocks, balances, tx status, nonces, verdicts) and states it is read-only over two chains, so the agent knows what class of data it returns. But it never explains why an agent should pick this tool over siblings like chainread__gas, chainread__balance or chainread__tx, which appear to cover the same ground, and the name 'block' implies a narrower scope than the description claims.

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 guidance and no exclusion of alternatives, despite nine chainread__* siblings covering individual resources. The description also never says whether the parameters select different sub-resources (the schema hints at /tx, /block, /batch) or whether they must be passed one at a time.

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