Solana: solanaBalances

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true, establishing this as a safe, read-only operation. The description adds that USD value is conditional on pricing availability, but does not disclose any behavioral traits beyond what annotations provide. No contradiction exists.

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?

The description is a single sentence that efficiently conveys the tool's purpose, scope, and output details. It front-loads the verb 'Return' and clearly lists the data fields, with no wasted words.

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?

Given the tool has no parameters and no output schema, the description adequately explains what the tool returns (native SOL + SPL tokens with specific fields). It could mention that it uses the connected user wallet, but that is implied. Overall complete for a simple balance checking tool.

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 input schema has zero parameters, so there is nothing to describe. Schema description coverage is 100% (trivially). Per guidelines, baseline for 0 parameters is 4, and the description does not need to compensate. It adds no unnecessary information.

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 clearly states the tool returns Solana wallet holdings including native SOL and all SPL tokens with specific fields (mint address, symbol, balance, decimals, USD value). It uses specific verbs ('Return') and resource ('user's Solana wallet holdings'), distinguishing it from sibling tools like solanaGetTokenPrices and solanaGetTokenPairPrice which focus on token prices rather than user holdings.

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 description provides no guidance on when to use this tool versus alternatives. It does not mention scenarios where it is appropriate or inappropriate, nor does it reference sibling tools like solanaGetTokenPairPrice for price-specific queries.

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