Get USDC balance

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

No annotations are provided, so the description carries the full burden. It explicitly discloses 'Read-only' (a key safety trait) and applies to 'any' address, implying no auth restrictions. However, it does not discuss error behavior, rate limits, or return details beyond the balance itself.

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?

Two short, front-loaded sentences deliver the essential purpose and a usage hint without any redundant words. Excellent structure.

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 read-only tool with one parameter, the description covers purpose, safety, and usage context. Lacks output format and error details, but these are relatively predictable from the tool name. The explicit 'read-only' compensates for missing annotations.

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 schema has only 'address' with minLength 1 and 0% description coverage. The description adds 'Base wallet address' but does not specify the expected format (e.g., 0x prefix, network specifics). More detail is needed to fully compensate for the missing schema description.

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 'Read-only USDC balance for any Base wallet address', which clearly describes the action (get balance), the resource (USDC), and the scope (Base wallet). This distinguishes it from sibling task-related tools.

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 instruction 'Check this before quoting a spend' provides clear contextual guidance on when to use the tool. It does not explicitly mention alternatives or exclusions, but the context is sufficient for a distinct read-only tool.

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