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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description adds nothing about safety or mutability. It also does not explain how 'notable collectors' is determined, whether results are paginated, or whether very large collections truncate the collector list — behavioral context an agent would want.

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 compact sentence with no filler, and the resource and payload are front-loaded. It is arguably too terse to be maximally useful, but there is no wasted wording to trim.

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 an output schema present, return values need not be explained, and the one required parameter is documented. However, for a tool surrounded by many closely-named OpenSea collection endpoints, the description leaves the agent guessing about its distinct scope and about what 'notable collectors' means operationally.

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 in the schema with an example (boredapeyachtclub). The description adds no syntax or format detail beyond the schema, 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 a specific resource (an OpenSea collection) and the exact data returned: follower count and notable collectors. It is clear what is being fetched, but it does not differentiate this from the numerous sibling tools that also take a collection slug, notably opensea_collection_holders, which sounds like the same audience data.

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 exclusion of alternatives, and no mention of when a caller should reach for this instead of opensea_collection, opensea_collection_holders, or opensea_collection_activity. The agent must infer usage from the name alone.

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