Get USDC balance

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

No annotations provided. The description only states it 'returns balance', with no disclosure of behavioral traits like rate limits, permissions, or response format. For a read query, minimal but acceptable.

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?

Single sentence that is front-loaded with the action and resource, no wasted words.

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?

The description is adequate for a simple balance query but lacks details on the return format (e.g., wei or decimal). No output schema exists to compensate.

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 100% for the single parameter, and the description does not add any extra meaning beyond the schema's 'EVM address (0x-prefixed, checksummed)'. Baseline 3.

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 clearly states the verb 'returns', the resource 'USDC balance', and specifies the network 'Base mainnet' and token type 'Circle native bridged USDC', distinguishing it from sibling 'balance' which likely gives native ETH balance.

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 implies use for USDC on Base but does not explicitly state when to use this vs alternatives like 'balance' (for native token) or 'usdc_recent_payments_to'. No when-not-to-use guidance.

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