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

Annotations already cover readOnly and openWorld, so the bar is lower. The description still adds real context: the report is evidence-based on verified OpenSea data, separates realized sales from listings, and may include missing data plus a confidence level — telling the agent results can be partial or uncertain. It stops short of mentioning cost/rate-limit behavior in the prose, which is left to the schema.

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 sentences, front-loaded with the core purpose and followed by a useful negative constraint. The single list-heavy sentence is dense but readable and wastes no words; a small structural refinement would earn a 5.

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?

There is no output schema, and the description compensates by enumerating what the report contains, including the confidence level and missing-data caveat. Parameters, payment tiers, and identifier formats are fully documented in the schema, so nothing essential for correct invocation is absent — only the paid-tier gating is unmentioned in prose.

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%, including detailed enum semantics for tier (free/full/auto with x402 payment mechanics) and chain. The description adds only the implication that the identifier resolves against OpenSea, so the baseline 3 applies; the schema does the heavy lifting.

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 and resource: it produces an evidence-based NFT collection risk report with named contents (market data, realized sales vs listings, creator evidence, risk flags, confidence level). An agent immediately knows what it gets back. It does not explicitly contrast with the sibling discover_new_nft_collections, so it falls just short of a 5.

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 only implied: analyzing an already-known collection. The one scoping statement, 'Not a profit prediction,' bounds expectations, but there is no explicit when-to-use guidance, no mention of the discovery sibling, and no note that paid tiers exist for full detail (that lives only in the schema).

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