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 clarifies that rows are curated and ranked against rarity and floor price, but omits return format, pagination, and any rate-limit/auth notes. With annotations carrying the safety burden, the added ranking detail is worthwhile but not rich behavioral disclosure.

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 with zero padding: the purpose and ranking basis come first, and the alternative-tool routing follows. 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?

With an output schema present, return values need not be described, and a one-param input plus the safety annotations are covered. The definition supplies purpose, ranking semantics, and sibling routing, leaving only minor gaps (pagination/result size) that are not critical to selecting the tool.

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% for the single slug parameter, so the schema already documents the input fully. The description adds no format or example detail beyond the schema, which is the expected baseline when structured data does the heavy lifting.

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?

Specific verb ('Fetch') plus a clearly scoped resource ('OpenSea's curated best-value listing rows for a collection'), and it explicitly distinguishes itself from sibling listing/rarity tools. An agent can tell what this returns versus opensea_collection_items or opensea_collection_rarest_items without opening any 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?

Names two concrete alternatives and the condition that selects each: opensea_collection_items for all listings, opensea_collection_rarest_items to rank by rarity. This is explicit when-to-use routing with no inference required.

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