1s_erc20_balance_live

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

It discloses that balances are returned as raw token units (divide by 10^decimals) and that non-standard tokens may return empty name/symbol. Since no annotations are provided, the description carries the full burden and offers useful behavioral insight.

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 concise sentences with no wasteful words; the first sentence states the main purpose, the second adds usage guidance and important notes.

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 simple balance lookup tool with three parameters, no output schema, and no annotations, the description provides sufficient information for an agent to understand the tool's purpose, usage, key behavioral details, and parameter effects.

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 parameter, but the description adds meaning by explaining the real-time nature, the balanceOf method, and the decimal conversion note, going beyond the schema.

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 states 'Get real-time ERC20 token balance directly from the blockchain via balanceOf' with a specific verb and resource, clearly distinguishing it from sibling tools like 1s_erc1155_balance_live.

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 advises using the tool for 'pre-transaction checks or when zero indexing delay is needed,' providing clear context but not explicitly naming alternatives.

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