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

With no annotations, the description carries the full burden. It discloses the price ($0.09 via x402), parallel execution, max of ten reads, and per-read failure reporting with a partial flag, explicitly stating 'a batch never claims success it did not have.' This is rich behavioral context beyond the schema.

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?

Three concise sentences, each adding value: cost/cap/parallelism, cost/latency comparison, and failure semantics. No filler or redundancy. The most important details are front-loaded.

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?

Given moderate complexity and no output schema, the description covers the essential context: what operations are supported, how failures are handled, and the payment requirement. It does not explicitly describe the return format, but for standard on-chain reads this is largely self-explanatory. The absence of auth details is mitigated by the payment mention.

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 input schema already covers 'chain' and 'reads' with formats, and the description reinforces those formats by enumerating the read types. The 'x_payment' parameter is not in the schema description, but the description mentions the $0.09 payment mechanism, which indirectly explains its purpose. This adds some meaning beyond the schema.

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 clearly states the tool performs batching of on-chain reads: 'up to TEN on-chain reads for ONE payment, run in parallel' and enumerates specific read types (balance, nonce, code, ERC-20, block number, gas price). This distinguishes it from sibling single-read tools like chain_native_balance or get_chain_nonce.

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?

The description provides a clear use case: batch multiple reads to save cost and latency, stating 'normally costs one payment per read; this is the same data for a fraction of the calls and the latency.' It does not explicitly name alternatives or state when NOT to use it, but the comparison implies batch use is preferred for multiple reads.

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