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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description usefully adds that results are cursor-paginated and that per-value item counts are returned, but says nothing about auth requirements, rate limits, or whether filters apply to this endpoint versus the items endpoint.

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 tight sentences: the primary capability is front-loaded and the sibling routing follows. No filler, and every clause carries 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?

An output schema exists, so return values need no explanation, and the description covers scope, pagination, and sibling disambiguation. The unresolved ambiguity about which filters actually apply to this endpoint is the only meaningful gap.

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 are already documented, making 3 the baseline. The description's generic statement that 'Filters can limit listings, prices, rarity, or selected traits' adds little beyond the schema and actually conflicts mildly with the schema labeling traits/price/rarity params as 'Items endpoint only'.

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 cursor-paginated trait type/value records and per-value item counts for an OpenSea collection slug'), which is a precise description of what the tool returns. It also explicitly names sibling tools and what each covers, so an agent can place it in the collection-tool family without opening schemas.

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?

It routes the agent to alternatives with their purposes ('use opensea_collection for metadata, opensea_collection_items for items, or opensea_collection_trait_offers for trait-based offers'), giving clear comparative context. It lacks an explicit when-not clause for this tool, but the sibling mapping makes the intended use inferable.

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