Get Wallet Balance

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

Annotations already mark readOnlyHint=true and destructiveHint=false; the description adds a user-auth prerequisite and specific HTTP errors (401, 503) plus retry backoff guidance. This materially enhances the safe-call context beyond what annotations provide.

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 compact sentences front-load the action and resource, with auth and error behavior following. No filler or unnecessary repetition of the title or schema.

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 parameterless read-only call, the description covers what is read, the required login, failure modes, and retry policy. While there is no output schema, the call itself needs no further input context.

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 tool has zero parameters, so schema coverage is vacuous and baseline for this dimension is 4. The description appropriately reinforces a parameterless call by focusing on auth and error handling.

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?

Description names the specific operation 'Read' and the exact resource 'authenticated user's on-chain ERC-20 wallet balance(s)', making the tool's function unambiguous. It also distinguishes itself from the unrelated sibling tools by stating the wallet-scoped subject.

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?

States the prerequisite auth: user-auth (log in first) and error conditions with retry advice. No explicit alternatives are named, but no sibling tool overlaps with wallet balance retrieval, so the practical use context is clear.

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