get_balance

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

The description unambiguously conveys a read-only operation ('Get'), consistent with the openWorldHint annotation. It adds useful context about the scope (native vs. ERC20 token) without introducing any contradictions or hidden behaviors.

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 that precisely states the tool's function with no unnecessary words or fluff.

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?

The description is sufficient for a simple read-only tool with no output schema. However, it does not help the agent distinguish this tool from similar sibling tools like evm_get_balance or get_token_balance, which would be a useful addition but is not strictly required given the straightforward nature.

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?

All three parameters are fully described in the schema (100% coverage), so the description adds no additional meaning beyond what the schema already provides. The reference to native currency and ERC20 tokens is duplicated in the tokenAddress field 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 uses the verb 'Get' with the specific resource 'balance of the wallet,' and clearly differentiates between native currency and a specific ERC20 token. This is not a tautology and distinguishes the tool from broader or less specific operations.

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 does not explicitly state when to use this tool versus alternatives such as evm_get_balance or get_token_balance, nor does it mention exclusions. It implies usage for checking wallet balances but provides no explicit contextual guidance.

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