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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and open-world nature are covered. The description adds a little context by indicating the results carry 'contract and collection details', but it says nothing about pagination behavior despite a cursor parameter, nor about rate limits or result freshness. With annotations carrying the safety profile, a 3 is appropriate.

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, zero filler, and the core purpose is front-loaded ahead of the alternative-tool routing note. Every clause earns its place.

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 described, and 100% schema coverage plus the read-only annotations mean the definition is nearly self-sufficient for a 3-param list tool. The only mild gap is the absence of any pagination hint tying the cursor param to a next-page flow.

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%, so all three parameters (type, limit, cursor) are already fully documented in the schema. The description only echoes the type values ('upcoming-mint or recently-minted') without adding format or syntax details, so the 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?

States a specific verb and resource ('Fetch OpenSea's upcoming-mint or recently-minted drop calendar') and names the closest alternatives (opensea_collection, opensea_activity), so the agent can tell what this tool is for without opening the schema. It does not distinguish itself from the many other opensea_* siblings (rankings, top_movers, collection_chart), so it falls short of full sibling differentiation.

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?

Explicitly names two alternative tools and what each is for ('opensea_collection for one collection or opensea_activity for collection and item activity'), which gives clear routing context. However, it states the routing conditions only implicitly and gives no explicit when-not to use drops (e.g. the difference between the drop calendar and a collection's own activity feed).

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