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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety and openness profile is covered. The description adds no behavioral context beyond what annotations and the schema provide (no pagination behavior, no rate limits, no freshness caveats). With the annotation bar lower, this neutral restatement lands at 3.

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 no filler. It is efficient, though arguably terse enough that it omits useful scoping information an agent would need.

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 not be explained, and annotations cover safety. For a four-parameter rankings tool, the description is minimally adequate but omits the usage/routing guidance that would make it complete against its many sibling discovery tools.

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%: ranking, timeframe, limit, and cursor are all documented inline, including defaults and allowed values. The description restates the ranking/timeframe concepts without adding syntax or format detail, so baseline 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 description gives a specific verb+resource ('Ranked OpenSea collections') and names the ranking dimensions it exposes. It clearly identifies itself as a rankings/leaderboard tool, distinct in kind from paginated collection listings. However, it does not name or contrast with any sibling such as opensea_collections or opensea_top_movers, leaving the routing distinction to inference.

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 when-to-use guidance, no statement of prerequisites, and no named alternative. The ranking/timeframe values are parameter options, not usage direction, so an agent gets no help deciding between this and the many sibling ranking/discovery tools.

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