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 adds nothing beyond that – no pagination behavior, no note on how keyword matching works, and no mention of the limit cap interactions beyond what the schema already states.

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, front-loaded sentence with no filler; the scoping clause ('inside one OpenSea collection') is placed immediately after the core action. It is efficient but so terse that it leaves behavioral and usage gaps unaddressed.

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 need not be described, and the required params are clear from the schema. However, for a search tool sitting among many similarly named OpenSea item/collection tools, the absence of any routing guidance leaves the definition only minimally complete.

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 slug, query, and limit are fully documented in the input schema itself. The description's 'keyword search' phrasing loosely maps to the query parameter but adds no format, syntax, or default detail beyond the schema. Baseline 3 applies.

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 ('Keyword search for items') and scopes it to one collection, which distinguishes it from collection-wide listing tools like opensea_collection_items. It does not name or contrast with the closely related sibling opensea_profile_search_items, so sibling differentiation is partial rather than explicit.

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?

The description gives no indication of when to prefer this tool over opensea_collection_items (which lists items) or opensea_profile_search_items (which searches a profile). There are no stated exclusions, prerequisites, or conditions for choosing it, leaving the agent to infer usage.

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