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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. Beyond that, the description adds genuinely new behavioral content: it returns two distinct buckets (available vs. pending) and is restricted to wallets the caller owns, which matters for interpreting results and errors.

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 front-loaded sentence with no filler; the scope constraint and the two balance categories are stated immediately. Nothing is redundant with the title or the annotations.

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 one-parameter read tool with a full safety annotation set and no output schema, this covers what the agent needs to select and call it: the currency, the two balance states, and the ownership constraint. It stops short of describing error cases for unowned wallets or whether results are chain-specific, which are the remaining minor gaps.

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 description coverage is 0%, so the schema gives only the name and type for walletId. The description partially compensates by implying the identifier must reference a wallet the caller owns and that exactly one wallet is in scope, but it says nothing about format, source, or failure behavior for that parameter.

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 names a specific verb (Read) and resource (available and pending USDC) plus scope (one owned wallet), which is far more precise than the bare name 'get_balance'. It does not explicitly contrast itself with near-neighbors like get_wallet or list_transactions, so the sibling differentiation is left implicit.

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?

Usage is only implied: the reader infers this is the balance-check tool and that it applies to a single owned wallet. There is no statement of when to prefer get_wallet or list_transactions, and no mention of what to do if the wallet is not owned.

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