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

Annotations already declare readOnlyHint=true and openWorldHint=true, covering the safety profile. The description adds nothing beyond that — no indication of the ranking window, sort order, chain scope, or whether results are cached/live, all of which matter for a 'most watched' list.

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 efficient sentence with no filler, front-loaded with the core concept. It is terse to the point of being under-specified rather than bloated, so it earns its brevity but at the cost of 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?

An output schema exists, so return-value details are not required. However, for a ranking tool in a dense OpenSea namespace, the description omits the ranking basis and scope, which are the one thing an agent cannot infer from the schema or annotations.

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% and the single 'limit' parameter is fully documented in the schema (range 1-100, default 20). The description adds no parameter meaning, so the baseline of 3 applies.

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 fragment 'Most watchlisted OpenSea collections' does name a specific resource and an implicit ranking criterion, so an agent can grasp the gist. But there is no verb and no differentiation from close siblings like opensea_rankings, opensea_top_movers, or opensea_collections, leaving the agent to guess how this list is scoped.

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?

There is no guidance on when to use this versus the many other OpenSea collection-listing tools. Usage is only weakly implied by the phrase 'most watchlisted'; no alternatives or exclusions are named.

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