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

With no annotations provided, the description carries the full behavioral burden. It adds useful context: the specific canonical contract, the cost ($0.003/call via x402), and the return shape (atomic and formatted values). It does not explicitly note read-only behavior or failure modes, but the balance-check nature is strongly implied and the provided details exceed minimal disclosure.

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, dense sentence delivers the core purpose, network, contract, return type, and pricing without redundancy. Every phrase earns its place and key information is front-loaded.

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 single-parameter balance check with no output schema, the description covers the essential operational facts: what is read, from where, what it returns, and what it costs. It could be more complete with explicit read-only clarification, but nothing critical is missing for correct invocation.

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?

The input schema has 100% description coverage for the single address parameter, so the schema already documents the parameter. The description does not add meaningful semantic detail beyond what the schema provides, warranting the baseline score.

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 states a specific verb ('Check'), a precise resource (a Base wallet's USDC balance on the canonical Base USDC contract), and the return format (structured JSON with atomic and formatted values). This clearly identifies what the tool does and distinguishes it from related siblings such as base_usdc_transfer_check and base_wallet_profile.

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 description gives no guidance on when to use this tool versus alternatives. It does not mention scenarios, exclusions, or recommend siblings for different needs, leaving the agent to infer the appropriate context from the name alone.

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