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

With no annotations, description carries full burden. It discloses cost and blockchain (Base) but omits authentication requirements, rate limits, error handling, or what happens with invalid addresses. The phrase 'or any ERC-20' is vague regarding token specification.

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?

Extremely concise single sentence with no wasted words. However, it could be slightly more structured (e.g., separating purpose and cost) but readability is good.

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?

Lacks output schema, so description should hint at return format. It does not. For a simple balance check, description covers core function and cost but omits error scenarios and response structure. Adequate but incomplete.

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%, so description must add value. It explains 'address' parameter context (on Base) and that 'token' can be ETH, USDC, or any ERC-20. However, it does not specify how to input token (symbol vs address) or default behavior if token is omitted.

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?

Description clearly states it retrieves ETH and USDC (or any ERC-20) balance for an address on Base, distinguishing it from sibling tools like base_allowance or base_token_info. The specific verb 'balance' and resource 'address on Base' make the purpose unambiguous.

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 explicit guidance on when to use this tool vs alternatives. It only mentions cost ($0.001) but does not specify scenarios where sibling tools like base_allowance or base_contract would be more appropriate.

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