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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is known; the second sentence usefully reinforces that no value moves or is credited. It adds the network/asset context (Base mainnet USDC) but says nothing about what happens if the wallet is not owned or what the returned instructions contain.

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 sentences, front-loaded with what is returned and immediately followed by the value-non-moving caveat. No filler or restatement of the tool name.

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 one-parameter read tool the description covers intent and the no-side-effect guarantee, which is most of what an agent needs. With no output schema, however, the shape of the returned "instructions" (text blob vs structured fields, and whether a claim step is included) is left unexplained.

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 single walletId parameter has no schema description (0% coverage), so the description must compensate. "For an owned wallet" does add the ownership precondition, which is genuine meaning beyond the schema, but it does not clarify the identifier format or what an invalid/foreign wallet id causes.

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?

Uses a specific verb ("Read") with a precise resource ("exact Base mainnet USDC transfer and claim instructions") scoped to "an owned wallet". An agent can distinguish this from the sibling claim_external_deposit by the read-only framing, though the sibling is never named.

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 framing implies this is the step you take before actually transferring or claiming, and "This does not move or credit value" hints at the boundary with claim_external_deposit. No explicit when-to-use/when-not statement or named alternative is given, so the routing is only implied.

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