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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds value beyond them by disclosing the shape of the returned data (four balance buckets plus recent ledger entries), which matters because there is no output schema. It does not mention auth or rate-limit behavior, but the token parameter covers the auth override case.

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, front-loaded with the resource and then the payload breakdown. Zero filler, no restatement of the tool name, nothing that could be removed without losing information.

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 zero-required-parameter read tool with rich annotations and no output schema, the description covers what an agent needs to decide to call it and what it will get back. Minor gaps remain: it does not say whose wallet is returned (the authenticated caller's) or that funds are test-only and non-withdrawable, which an agent might otherwise assume.

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 100% and the single optional 'token' parameter is thoroughly documented in the schema, including the guest requester_token follow-up case. The description adds no parameter meaning beyond that. Baseline 3 is appropriate when the schema does the heavy lifting.

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 the specific resource (your test USDC wallet) and enumerates exactly what it exposes: available balance, escrowed funds, earned, spent, and recent ledger entries. That is far more concrete than the bare name 'wallet' and lets an agent tell it apart from write-oriented siblings like faucet or receipt_proof. It stops short of explicitly contrasting with those siblings, so it is a strong 4 rather than a 5.

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?

There is no when-to-use guidance at all: no statement that this should be called to check funds before posting a request, and no pointer to the obvious alternative, faucet, for obtaining test USDC. Usage is only inferable from the title. That is below the 'implied usage' bar of 3.

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