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

With no annotations, the description carries the burden and does well: it discloses the 20-call cap, that each call individually returns success/decoded/raw hex or its revert reason (implying partial-failure tolerance rather than all-or-nothing), and the pricing/auth model ($0.004 USDC per call via x402 on Base). What's missing is whether mixed-chain calls are rejected, and any rate-limit or wallet-setup detail for x402.

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?

Two sentences, front-loaded with capability and scope, then return semantics, then pricing. No filler; each clause carries information an agent needs before calling.

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 paid batch RPC tool with no output schema and no annotations, the description covers the essentials: batch limit, per-call result shape including revert handling, chain constraint, and cost model. Only edge behavior (mixed-chain rejection, whole-request failure modes) is left unstated.

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 100%, so the baseline is 3. The description adds only the repeated 20-item cap and the 'one chain' constraint (all calls share the chain parameter); it adds no meaning about args encoding, function signature format, or blockTag behavior beyond what the schema already states.

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?

States a specific verb and resource ('Up to 20 contract reads on one chain in a single Multicall3 request') and clarifies the batching mechanism, which cleanly separates it from the single-read sibling chainread_read_contract. It doesn't explicitly name the sibling, but the batching scope makes the distinction obvious.

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 'up to 20 reads on one chain' framing implies the batch use case (and implicitly that single reads belong elsewhere), but there is no explicit when-to-use/when-not guidance and no named alternative such as chainread_read_contract. Adequate but inferential.

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