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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=true), so the description focuses on useful behavior: it discloses the pagination mechanism, the next_page_cursor field name, and that filters combine. It omits auth requirements and rate limits, which keeps it below 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?

Front-loaded with the return payload, then pagination, then filters, with every sentence doing work. The trailing 'slug: ... limit: ...' restates the schema descriptions verbatim, which is minor redundancy given 100% schema coverage.

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, the return-value burden is off the description, yet it still summarizes the payload and fully explains pagination and filter combination. An agent has everything it needs to invoke the tool correctly.

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 the baseline is 3, but the description adds real value beyond the schema by explaining the combination semantics of the filters and giving a concrete example (traits=Fur:Solid Gold&listed_only=true) plus identifying cursor as sourced from next_page_cursor.

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 ('Returns a cursor-paginated page of NFTs in a collection') and enumerates the payload contents (traits, rarity rank, owner, best listing, last sale price). It also names the sibling opensea_collection_search_items, so an agent can distinguish it without opening either 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?

Provides clear usage context: page forward with cursor, narrow results with specific filters, and use opensea_collection_search_items for searching inside a collection. The alternative is named but the exact condition that should route to it versus this tool is only implied, not spelled out.

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