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

Annotations only declare readOnlyHint=true, so the description adds real value beyond them: the two-step unpaid-then-paid handshake and where the signed payment must be placed. It does not cover failure modes (invalid token, reverts), but for a read tool the payment protocol disclosure is substantive.

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?

Reasonably front-loaded with the core purpose first, but it redundantly re-specifies token and address details already fully covered by the schema, and the endpoint URL line adds little for an agent that already has the tool bound.

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?

No output schema exists, yet the description supplies a measured output example showing the result shape ('result': '70000'), plus the payment protocol. An agent has everything needed to call and interpret this simple two-param read.

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 100%, so the schema already documents token and address. The description restates them with the same '0x + 40 hex' detail, adding no meaning beyond the schema; baseline 3 applies.

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?

Names a specific verb (read balanceOf), resource (Base ERC-20 token balance), and scope (holder address on Base). It is clearly distinguishable from siblings like base_erc721_ownerof, base_eth_getbalance, and the eth_mainnet erc20_balanceof variant.

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?

Provides concrete invocation context for the x402 payment flow: call once without payment to receive terms, then retry with the signed payment at _meta['x402/payment']. However, it gives no guidance on when to prefer this over alternatives such as network_info_balance_bundle or eth_mainnet_erc20_balanceof.

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