execute_multicall

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states batching in a single transaction but does not explain that this executes a state-changing on-chain transaction, potential revert/atomicity behavior, gas costs, or what the return value looks like. This is a significant gap for a mutating contract tool.

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 a single sentence that gets straight to the point. It is front-loaded, uses no filler, and is appropriately sized for a tool with only two parameters.

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 transaction-executing tool, the description is under-specified. With no output schema and no annotations, the agent is left without information about return values, failure behavior, or whether this broadcasts a real transaction. Sibling tools like write_contract or simulate_transaction suggest nuance, but this tool's description does not clarify where it fits.

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 provides 100% coverage with descriptions for both parameters (calls, network). The tool description adds no additional parameter semantics beyond what the schema already states, so a baseline score of 3 is appropriate.

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 uses the specific verb 'Execute' and the resource 'multiple contract calls in a single transaction', clearly distinguishing it from sibling single-call tools like read_contract, write_contract, and simulate_transaction. It is concise yet unambiguous about its core function.

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 implies usage when multiple contract calls need to be batched into one transaction, but it provides no explicit guidance on when to choose this tool over individual calls or alternatives like simulate_transaction. There are no when-not conditions or alternative tool references.

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