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

With no annotations provided, the description carries the transparency burden. It discloses that the operation is a read via balanceOf, is scoped to one wallet, and costs $0.003 USDC via x402. It does not mention return format, units, or error behavior, but covers the key behavioral aspects of a simple read 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?

A single front-loaded sentence places the action and object first, then the method and cost. Every word earns its place with no filler.

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 two-parameter read with no output schema, the description gives the core information needed to invoke it correctly. It could be more complete by stating whether the balance is returned in raw units or with decimals and by flagging the native-balance sibling, but nothing critical is missing.

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 description coverage is 0%, but the description adds role-level meaning: token is the ERC-20 contract and address is the Base wallet. It does not provide units, decimals, examples, or address format guidance, so it only minimally compensates for the missing schema descriptions.

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 begins with a specific verb, 'Read', and a precise resource: an ERC-20 token balance for one Base wallet using balanceOf. This clearly distinguishes it from siblings like base_wallet_balance (likely native balance) and base_erc20_transfers (transfer history).

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 usage context is implied: use this when you need an ERC-20 token balance for a single Base wallet. However, it does not explicitly state when not to use it, such as for native ETH balances, or name an alternative tool.

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