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

Annotations already declare read-only and idempotent behavior, but the description adds substantial context: per-call cost (0.005 USDC), x402 payment mechanism (no account/key), pre-payment validation, no charge on failure, and the x402 PaymentRequired response without payment. It also points to a free sample via get_example. This goes well beyond structured annotations.

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 front-loaded with the core purpose and return contents, followed by pricing, sample, and HTTP alternative. It is efficient and well-structured, though the HTTP URL adds slight length without being essential for tool invocation.

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 complexity of a paid financial data tool with no output schema, the description fully covers what is returned (symbol, name, amount, price, value, total, NFT count), payment flow, error handling, and a free sample path. Nothing an agent needs to call it correctly is missing.

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%, so both parameters (address, min_usd) are already documented in the schema. The description does not add format details or validation rules beyond the schema, and min_usd is not mentioned in the description. Baseline 3 is appropriate when schema carries the parameter semantics.

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 a specific resource—a Solana wallet's full token portfolio valued in USD—and lists exactly what is included (SOL, fungible SPL/Token-2022 balances, total value, NFT count). It distinguishes itself from simpler siblings like wallet_balance by emphasizing completeness and sorting.

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 phrase 'One call instead of dozens of RPC reads' implies usage for comprehensive portfolio retrieval, but the description does not explicitly name when to use this tool versus siblings such as wallet_balance or solana_token_check. No exclusions or alternative routing are provided.

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