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

Annotations already declare readOnlyHint=true and openWorldHint=true, and an output schema already documents the return shape, so the description's list of returned fields (traits, rarity, owner, best listing, last sale) is largely redundant. It adds no behavioral context such as pagination semantics via cursor, listing-price filtering behavior, or rate limits.

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 wasted words, and the key content (collection items plus returned fields) leads. It is efficient, though being an incomplete phrase rather than an explicit verb phrase slightly limits clarity.

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 12-parameter tool with full schema documentation, complete annotations, and an output schema, the description is adequate but minimal. It omits any guidance on the many filter/price/rarity options and how they interact, which is the main thing an agent would still need beyond the schema.

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 12 parameters (including the 'Items endpoint only' distinctions on traits, price, rarity, and listed_only) are already fully documented in the schema. The description adds no parameter meaning beyond that, 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 description names the resource (items in an OpenSea collection) and enumerates the returned data (traits, rarity, owner, best listing, last sale), so the agent knows what it retrieves. However, it does not distinguish this tool from close siblings like opensea_collection_search_items or opensea_collection_rarest_items, which fetch overlapping item sets. Clear purpose but no 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?

There is no guidance on when to use this tool versus alternatives such as opensea_collection_search_items or opensea_collection_rarest_items, nor any mention of prerequisites like needing a valid slug. The description is purely descriptive of contents, leaving routing to sibling tools entirely to inference.

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