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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds only the qualifier 'recorded', hinting at historical rather than live data, but gives no detail on whether sales are limited, ranked, or windowed. Some added context, but thin.

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, front-loaded sentence with the resource and metric placed first. No filler, though it is arguably too terse to be maximally useful.

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?

An output schema exists, so return-value explanation is not required, and the schema fully documents the lone parameter. Still, for a collection-analytics call in a dense sibling cluster, the description omits the scope of 'top' (count, time range, ranking basis), which an agent needs to invoke it correctly versus alternatives.

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 a single required 'slug' parameter already documented in the schema with an example, so the description carries no additional parameter burden. Baseline 3 applies; the description adds nothing beyond the schema.

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 metric (highest-value recorded sales) tied to a specific resource (an OpenSea collection), which is more precise than a generic 'get sales'. However, it does not differentiate itself from close siblings such as opensea_collection_activity, opensea_collection_best_deals, or opensea_collection_chart, leaving overlap for an agent to resolve.

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 guidance, no exclusions, and no mention of alternatives. The description never says whether this is a top-N ranking, whether it covers a time window, or when an agent should prefer this over collection_activity or best_deals.

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