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

No annotations exist, so the description carries the full behavioral burden. It discloses only a trial quota ('5 free trial calls per signed wallet'), which hints at an auth/payment requirement, but says nothing about what a signed wallet means, error behavior, rate limits, or response shape for a read operation.

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?

The core purpose is front-loaded in one compact sentence, but the trailing promo line with the emoji ('5 free trial calls per signed wallet') is marketing noise rather than task-relevant content.

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?

A three-parameter tool with no annotations, no output schema, and no required-parameter guidance gets too little from this description. It should at least clarify how to supply the wallet/address and what the ERC-20 result set looks like.

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 0% and there are three parameters, yet the description only loosely maps to 'chain' (Base or Ethereum) and 'wallet'. It never explains the 'address' parameter or how it differs from 'wallet', leaving a real ambiguity unresolved.

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?

States a specific verb and resource: returns known ERC-20 balances (e.g. USDC) for a wallet on Base or Ethereum. That is enough to distinguish it from siblings like x402-wallet-balance (native balance) or x402-wallet-nfts, though it never names an alternative explicitly.

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?

No when-to-use guidance and no mention of alternatives such as x402-wallet-balance, x402-multi-balance, or x402-wallet-scan. The only contextual cue is that it covers ERC-20 tokens on two chains, which an agent must infer on its own.

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