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 adds that the payload includes floor price, top offer, and rolling stats, but that content overlaps with the output schema, and it discloses nothing about rate limits, freshness, or failure behavior for a missing slug.

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 tight sentence that front-loads the resource and lists the key data points without filler. It is appropriately sized, though the fragment lacks a verb, which slightly weakens actionability.

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?

With a full output schema, annotations for safety, and a fully documented single parameter, the description only needs to convey what the tool is for, and it does. It is complete for this low-complexity read tool, with sibling disambiguation being the only real omission.

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% and the single slug parameter is fully documented with an example in the schema itself. The description adds no parameter information, 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?

The description names the resource (OpenSea NFT collection) and enumerates the specific data returned (metadata, floor price, top offer, rolling trading stats), so an agent knows what it fetches. It is a noun phrase rather than a verb, and it does not distinguish itself from the many opensea_collection_* siblings (activity, chart, holders, traits), so sibling differentiation is absent.

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 when-to-use guidance, no prerequisites, and no mention of alternatives. The agent is left to infer that this is the collection-level detail tool and must guess whether opensea_collection_chart, opensea_collection_activity, or opensea_search_collections is the right choice.

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