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

Beyond the annotations (read-only, idempotent, non-destructive), the description adds meaningful behavioral context: results are spam-filtered, data comes via Covalent, calls are priced at $0.02 via x402 on Base, prepaid headers unlock unlimited calls, and no wallet or API key is required. This gives the agent important operational expectations the annotations alone do not convey.

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 and mostly efficient, but the opening phrase 'NFT collections held by a wallet (+ floor)' is somewhat redundant with the immediate follow-up sentence. The pricing, header, and free-tier information is valuable, so the overall length is justified despite minor redundancy.

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 a clear purpose, explicit input requirement, pricing model, authentication/header instructions, and an output schema available, the description is fully sufficient for an agent to select and invoke the tool correctly. Nothing essential 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?

The schema already documents the single address parameter at 100% coverage with 'Wallet address'. The description merely repeats 'Required input: address' and does not add format, network, or validation details beyond the schema. This matches the baseline for full schema coverage.

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 opens with a precise noun phrase and then a full sentence: 'Lists the NFT collections a Base wallet holds — name, count and floor value'. It identifies the resource (Base wallet NFT collections), the action (lists), and the output dimensions, clearly distinguishing it from general wallet-token or portfolio tools.

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 description states the intended context: 'For agents profiling a wallet's NFT exposure.' This is clear guidance on when to use the tool, though it does not explicitly name alternatives or exclusion conditions. Given the sibling list contains related tools like wallet_tokens and nft_floor, a slightly more explicit contrast would have earned a 5.

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