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

With no annotations, the description carries the full burden and does meaningful work: it discloses the $0.001 USDC per-call cost (critical for an agent's budget decisions) and signals a read-only, non-mutating operation via "get" and "lightweight check." It does not mention rate limits or whether the wallet must exist / what happens on an invalid address, leaving minor gaps.

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?

Three short sentences, front-loaded with the capability, then the use case, then the cost. Nothing is redundant and each sentence contributes distinct 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 one-parameter read tool with no output schema, the description conveys what is returned (SOL plus all token balances), when to call it, and its cost — enough for correct invocation. Missing only edge-case behavior such as empty wallets or invalid addresses.

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 coverage is 100% and the single walletAddress parameter is fully documented as a base58 Solana address, so the schema does the heavy lifting. The description adds no format or validation detail beyond implying a single wallet scope; baseline 3 applies.

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?

States a specific verb+resource+scope: SOL balance plus all token balances for a single Solana wallet. It is distinguishable from nearby siblings like wallet_pnl or wallet_profile by being a raw balance read, though it never names those siblings explicitly to draw the line.

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?

"Use before transactions to verify sufficient funds" gives a concrete trigger context. It stops short of stating when not to use it or naming an alternative (e.g., wallet_profile for historical holdings), so it is clear but not fully routing.

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