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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds real behavioral context the annotations don't: cursor pagination, quantity-based ranking, and the fact that results expose public wallet addresses and display names. It doesn't mention rate limits or whether holders can be filtered by address, so it stops short of a 5.

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 dense sentences, zero filler, with the core action front-loaded before the sibling routing. Every clause earns its place.

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 needn't be spelled out, and the pagination model plus rankings are described. The omission is the discrepancy between the description's filter claim and the schema's 'Items endpoint only' labels, which leaves some ambiguity about which filters actually apply here.

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 the schema already documents all 12 parameters and the baseline is 3. The description only summarizes them loosely ('Filters can limit traits, price, or listing state'), and that summary is arguably misleading for a holders endpoint because the schema labels traits/price/listing params '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+resource ('Fetch ... OpenSea holder records for a collection slug'), plus scope (cursor-paginated, ranked by quantity) and the returned fields (wallet addresses, display names). It also names the three sibling tools it is not, so an agent can distinguish it without opening a schema.

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?

Explicitly routes the agent: use opensea_item_owners for a single item, opensea_collection_items to browse items, opensea_collection_social_proof for holder evidence. The when-to-use-this vs alternatives condition is stated, not inferred.

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