Read state from one or many contracts via a single multicall

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false. The description adds valuable behavioral context, such as the clause format, address override behavior for erc20/erc721, return format (success, primary value, decoded array), and bigint stringification. No contradiction with annotations.

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 description is two sentences, front-loaded with the purpose, then providing detailed breakdown. It is appropriately sized and each sentence adds value. Slight room for improvement in structuring the details, but overall concise and effective.

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 the complexity (one parameter with nested objects, many sibling tools), the description sufficiently explains usage, conventions, and output format. The presence of an output schema reduces the burden for return value documentation, but the description still adds clarity on return structure. It is complete enough for correct tool invocation.

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% with descriptions for each field. The description goes beyond by explaining the purpose of each clause field, the special meaning of 'address', and the return structure. This adds meaning beyond the schema, such as the fact that bigint values are stringified.

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 executes read-only contract calls in a single multicall, which is distinct from sibling tools that perform individual contract reads. The verb 'execute' and resource 'read-only contract calls' are specific, and the title emphasizes multicall aggregation, distinguishing it from single-call tools.

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 explicitly advises using this tool 'instead of one call per round-trip whenever you need multiple values.' This gives clear context for when to prefer it. It does not explicitly list when not to use it, but the guidance is sufficient given the sibling tools.

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