multi_token_balance

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

No annotations are provided, so the description bears the full burden. It mentions a 'single Multicall3 round-trip' implying efficiency and atomicity, but lacks details on error handling, rate limits, max tokens, or side effects. The description is insufficient for full behavioral transparency.

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?

A single, clear sentence with no redundant information. It efficiently conveys the tool's purpose and advantage (Multicall3).

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 simplicity of the tool, the description is moderately complete. It lacks details on maximum token count, return format, and chain context. For a basic read operation, this is acceptable but could be more informative for an AI agent deciding between siblings.

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 50% (only 'tokens' has a description). The description adds meaning for 'address' by referring to 'one address's balance', clarifying it is the wallet address. However, it does not specify the format for tokens beyond what the schema already provides. This partially compensates for the missing schema description.

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 reads an address's balance across several tokens in a single Multicall3 call. It uses a specific verb ('read') and resource ('balance across several tokens'), and differentiates from sibling tools like get_token_balance (single token) and list_token_holdings (likely all tokens).

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 when to use this tool (for multi-token balance queries), but it does not explicitly state when not to use it or provide alternatives. For example, it could mention that for a single token, use get_token_balance instead.

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