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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds genuinely new behavior: compressed NFTs are included, likely spam airdrops are filtered by default, results are grouped by collection, and each call costs $0.003 USDC via x402.

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?

A single dense sentence that front-loads the resource and then packs in scope, filtering defaults, and cost. The colon-chained clauses are slightly heavy but every element carries 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?

With no output schema, the description usefully previews returned fields (name, image, collection, grouping) and discloses the payment requirement and spam default. Only pagination/limit behavior and sibling differentiation are 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 coverage is 67%, with limit undocumented anywhere. The description clarifies the spam default (relevant to include_spam) and the collection grouping, but adds nothing about wallet format, limit semantics, or result sizing.

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 resource and scope: NFTs owned by a Solana wallet, with the notable addition of compressed NFT coverage. It does not differentiate from plausible siblings such as nft or wallet_nfts, so an agent must guess which NFT tool applies.

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 'owned by a Solana wallet', and the cost line tells the agent this is a paid x402 call. However, it never says when to prefer this over siblings like nft, wallet_nfts, or solana_wallet, nor any prerequisite beyond payment.

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