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

No annotations are provided, so the description carries the full behavioral burden. It conveys only that this is a Base USDC read; it says nothing about return units (raw 6-decimals vs human-readable), behavior for invalid/unchecksummed addresses, error cases, or rate limits.

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?

One sentence with the resource and network scoping front-loaded, followed by a short parenthetical. The ETH comparison is mildly promotional but does serve routing, so nothing is truly wasted.

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 single-parameter read tool with a fully described schema and no output schema, the essentials are present. It still omits anything about the return value's format, which matters for a token balance where decimal scaling is ambiguous.

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?

With a single parameter and 100% schema description coverage, the schema already defines 'address' as an EVM address (0x + 40 hex). The description adds only the chain context, so the baseline of 3 is appropriate.

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 and resource ('Get USDC balance of an address') and pins the network ('on Base'), which is a real differentiator among these chain-query siblings. The parenthetical contrast with ETH implies it is not the same as get_balance, but it does not name that sibling 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?

'More useful than ETH for most agents' is an implicit steer toward choosing this over a native-balance tool, but there is no explicit when-to-use or when-not-to-use statement, and no alternative is named. Usage is inferable rather than stated.

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