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 useful semantic context about what the data represents (watchlisting precedes buying) and that floor price/stats are included, but discloses no operational behavior such as sorting order, freshness/latency, or pagination limits.

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?

Front-loaded with the core purpose, then the rationale, then routing to a sibling; every sentence is short and purposeful. The only waste is restating the limit parameter, which the schema already documents fully.

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 values need no explanation, and the description covers purpose, data content, and an alternative. What it lacks is scoping detail an agent might want (e.g., chain scope or whether results are global), but for a zero-required-parameter list tool it is adequately complete.

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?

There is a single optional parameter with 100% schema description coverage, and the description's 'limit: Collections to return, 1-100. Defaults to 20.' is a verbatim restatement of the schema entry. Baseline 3 applies since the schema already does all the work and the description adds no new meaning.

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 ('Returns the collections most added to watchlists on OpenSea') plus the payload ('current floor price and headline stats'). It explicitly distinguishes itself from the sibling opensea_rankings, so an agent can pick between them without opening either schema.

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?

Gives the interpretive context for when this signal is valuable ('a demand signal that leads trading volume') and names an explicit alternative ('Use opensea_rankings to list ranked OpenSea collections'). It does not state when this is the wrong choice versus other ranking-like siblings such as opensea_top_movers, so it stops short of full when/when-not guidance.

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