opensea: openseaGetTrendingCollections

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

Annotations clearly indicate read-only, non-destructive, idempotent, and open-world behavior. The description adds 'Find trending...' and 'market research,' which aligns with these traits but does not disclose additional behavioral details like pagination limits or chain-specific constraints beyond what the schema provides.

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 concise sentences that immediately state the purpose and usage context. Every word adds value, with no redundancy or extraneous 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?

Given the tool's simplicity, good annotations, and full schema coverage, the description is largely complete. It could mention the next parameter for pagination, but that is documented in the schema. The description adequately covers the core functionality and intended use.

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?

All parameters have schema descriptions (100% coverage), so the description does not need to elaborate much. It briefly references the sorting metrics ('by volume, market cap, or price changes') which aligns with the orderBy enum, but adds no new detail 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?

The description clearly states the action ('Find trending NFT collections') and the resource ('NFT collections'), with specific criteria ('by volume, market cap, or price changes'). It distinguishes this tool from sibling OpenSea tools like openseaGetCollectionStats and openseaGetCollectionActivity by focusing on trending collections for market research.

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?

The description suggests using it for 'market research and discovering popular collections,' which implies appropriate usage. However, it does not provide explicit guidance on when not to use it or mention alternatives, such as using specific collection data tools (e.g., openseaGetCollectionStats) for detailed stats on a single collection.

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