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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and external-data behavior are covered. The description adds the ranking criterion (quantity held), which is genuinely useful ordering context the annotations do not convey, but it says nothing about pagination behavior despite a cursor parameter, or about result size 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 compact clause with the resource and ranking front-loaded and no filler. It is a fragment rather than a structured description, but nothing in it is wasted.

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-value explanation is not required. However, for a 12-parameter tool whose schema includes several parameters that do not apply to this endpoint, the description leaves gaps around pagination and parameter applicability.

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 coverage is 100%, so every parameter is already documented in the schema, which sets the baseline at 3. The description adds no parameter meaning; notably it does not clarify that many schema parameters (traits, price/rarity bounds, listed_only, event_types) are flagged 'Items endpoint only' and are irrelevant to this holders endpoint.

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 states a specific resource (wallets holding items in a given OpenSea collection) and a specific ordering (ranked by quantity held), so an agent knows exactly what data comes back. It does not, however, distinguish this from closely related siblings such as opensea_item_owners or opensea_collection_social_proof.

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. With dozens of opensea_* siblings, an agent gets no help deciding between this tool, opensea_collection_items, or opensea_item_owners.

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