get_token_balance

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

Beyond readOnlyHint annotations, description reveals that balances are already formatted (decimals applied), avoiding common error of re-dividing. Also warns about deprecated addresses and automatic symbol resolution.

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?

Single, well-structured paragraph with clear purpose, usage guidance, and important warnings. Every sentence adds value without redundancy.

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 read-only balance tool with 4 optional parameters and no output schema, description covers token selection, address usage, return format, and deprecation warnings comprehensively.

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 covers descriptions (100%), but description adds practical guidance: prefer token over tokenAddress, automatic resolution, deprecation warning for USDD. Adds value over raw 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 clearly states it gets TRC20 token balances for an address, specifying token symbol or contract address. It distinguishes itself from sibling tools like get_trx_balance (for TRX) by focusing on TRC20 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?

Explicitly advises to prefer token symbols over raw addresses to avoid deprecated contracts, e.g., USDD. Implicitly distinguishes from related tools (get_trx_balance, check_allowance) but no explicit when-not-to-use.

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