opensea: openseaGetCollectionStats

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

Annotations already declare readOnlyHint, non-destructive, idempotent, and openWorld. The description adds specific data fields returned (floor price, volume, etc.), which is helpful but does not disclose rate limits, authentication needs, or data freshness. With strong annotation coverage, the description's extra behavioral context is adequate but not exceptional.

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, well-structured sentence that conveys the purpose, what data is returned, and a critical usage rule. No unnecessary words.

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?

For a simple stats tool with one parameter and no output schema, the description lists key return fields (floor price, volume, sales, owners, market cap), giving a good sense of the output. It does not detail the full output structure, but that is acceptable for this level of complexity.

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?

The single parameter (collectionSlug) has 100% schema description coverage explaining the slug format. The tool description adds a warning against using the collection name, which is a minor improvement. Since schema coverage is high, the baseline is 3, and the description offers only marginal extra 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?

The description clearly states the tool retrieves detailed NFT collection stats including specific metrics (floor price, volume, sales, owners, market cap), and distinguishes it from siblings like openseaGetTrendingCollections or openseaGetCollectionActivity by its focus on aggregate stats.

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 provides a key usage hint: use collection slug, not the collection name. However, it does not explicitly state when to use this tool versus alternatives (e.g., for individual listings or activity). The context is reasonably clear given the tool's purpose.

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