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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds genuine behavioral context beyond them: the output is bounded to the 10 most recent transactions and includes USD valuation and a tracked total, which tells the agent what to expect from a call. It stops short of mentioning rate limits, truncation beyond the transaction cap, or behavior on invalid/empty addresses.

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 verb and the returned payload, with zero filler. Every clause carries content an agent needs (balance, holdings, USD values, total, transaction cap).

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?

With no output schema, the description carries the return-value burden and does so thoroughly by enumerating the four output components. It omits error behavior (invalid address, empty wallet) and whether the 10-transaction list is paginable, which keeps it just short of fully complete for a read-only inspection 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?

Schema coverage is 100% and the single parameter (base58 address) is fully documented in the schema. The description restates the resource as a 'Solana wallet address' but adds no format, validation, or constraint detail beyond what the schema already provides, so the 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?

The description names a concrete verb (Return) and resource (SOL balance, token holdings, transactions for a Solana wallet address) and enumerates the payload precisely. It is unmistakable what the tool does, but it never distinguishes itself from the siblings check_token or explain_transaction, which cover adjacent ground.

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 statement, no prerequisites, and no routing to alternatives. With siblings like check_token (token-level detail) and explain_transaction (single-tx detail) present, the absence of any 'use this for a full wallet overview' framing leaves selection to inference from the name alone.

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