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

Annotations already establish readOnlyHint and openWorldHint, so the safety profile is covered. The description adds real behavioral scope beyond that: only currently listed (not all) items, ordered by rarity, with traits and asking price. It stops short of noting pagination, listing-count limits, or freshness, so not a full 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 sentences with no filler. Scope and ranking are front-loaded, and the sibling routing follows immediately. 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?

For a read-only, single-parameter fetch tool with an output schema and annotations covering safety, the description supplies everything needed: scope (listed items only), ordering (rarity), and payload (traits plus price), plus disambiguation from siblings.

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?

Only one parameter (slug) and schema description coverage is 100%, so the schema already documents format and the required flag. The description adds no slug syntax or collection-resolution nuance beyond the schema, which is the expected baseline when schema does the work.

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 and resource -- fetching currently listed items in a collection ranked by rarity -- and explicitly names which siblings cover the adjacent use cases (opensea_collection_items, opensea_collection_best_deals). An agent can pick this tool 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?

Second sentence gives explicit routing: use opensea_collection_items for all listings, or opensea_collection_best_deals for the curated rarity-versus-floor shelf. That makes the when-to-use decision unambiguous among three closely-related sibling tools.

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