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

With no annotations supplied, the description carries the full burden and does well: it discloses the x402 payment requirement and exact price ($0.005 USDC on Base), the value-based sort order, that dust/unpriced/empty accounts are aggregated rather than listed, and — importantly — that transaction history is capped at the newest 1,000 with a flag when more exists. Missing only failure modes or rate/error behavior.

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?

Every clause is substantive — truncation caps, aggregation, pricing — so nothing is padding. But it is delivered as one sprawling run-on sentence chained with 'plus ... plus ...', which hurts front-loading and scanability. Content earns its place; the structure does not.

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?

No output schema exists, so the description must characterize return values, and it does so exhaustively: balance composition, USD valuation source, sorting, aggregation buckets, transaction recency stats, history-truncation flag, and deployer/funded-deployer extras. An agent knows exactly what it will get and what its limits are before paying.

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?

There is a single parameter with 100% schema description coverage, and the schema already states the base58 Solana address format and pattern. The description adds no format, validation, or example detail beyond that. Baseline 3 is correct when the schema fully documents the parameter.

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: portfolio and activity of a Solana wallet, enumerating SOL/SPL/Token-2022 balances with Jupiter USD pricing plus transaction recency metrics and deployer history. An agent can tell this is the Solana wallet lookup rather than a token-level tool like solana_token_snapshot. It loses the top mark because it never names the alternative tools it overlaps with (deployer_record, deployer_links), leaving that differentiation to inference.

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?

Usage is implied by the scope: supply a wallet address when you need holdings, activity, or the wallet's deployment history. There is no explicit when-to-use/when-not statement and no pointer to solana_token_snapshot or deployer_record when the caller actually wants token- or deployer-centric data. The detailed contents list partially compensates by letting an agent self-select.

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