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

With zero annotations, the description carries the full burden and does it well: it discloses the exact per-call cost ($0.008 USDC), the payment rail (x402), the network (Solana mainnet), and the data provider (Helius DAS). This is meaningful behavioral context beyond the name. It omits failure modes and rate limits, but the cost disclosure is the critical behavioral trait for a paid tool.

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 tight sentences with zero filler. The core content is front-loaded in the first sentence, and the cost disclosure earns its place in the second. Every word adds 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, the content enumeration and cost disclosure cover a lot. However, there is no output schema, so the description doesn't hint at return structure or pagination, and it gives no guidance on alternatives like get_wallet_activity. These are notable gaps given no annotations exist to fill them.

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 description coverage is 100%, with the 'wallet' parameter already documented as a base58 Solana address. The description adds no parameter-level detail beyond confirming the Solana context, so the schema carries the load. Baseline 3 is appropriate.

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 states the resource (Solana wallet holdings) and precisely enumerates what's returned: native SOL, SPL tokens with USD values, and NFT count via Helius DAS. This content spec makes it distinguishable from siblings like get_wallet_activity or get_token_holders, though it never names them explicitly.

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?

No when-to-use or when-not-to-use guidance is provided, and no alternative sibling tools are named. The cost disclosure ($0.008 per call) implicitly signals this is a paid call to use judiciously, but the description doesn't help an agent choose between this and wallet- or token-related siblings.

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