opensea_collection_traits

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

No annotations are provided, so the description carries the burden. It discloses that results are cursor-paginated, that item counts are included only where OpenSea publishes them, and that numeric traits carry a comparison operator. However, it doesn't mention rate limits, whether the tool is read-only, or what happens with invalid slugs.

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?

The description is two sentences, front-loads the main action, and packs useful detail (pagination, counts, numeric operator) without fluff. It earns its place, though it could be slightly more explicit about usage context.

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 simple read-only list tool with 100% schema coverage and no output schema, the description covers the key behavioral aspects (pagination, counts, numeric operators). It lacks explicit guidance on when to choose this over sibling trait-related tools, and doesn't mention error cases or rate limits, but these are minor for this tool's complexity.

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 the schema already documents all three parameters. The description adds context about pagination ('cursor-paginated page') and the meaning of limit ('Trait types per page'), but doesn't add much beyond the schema's own descriptions. Baseline 3 is appropriate.

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 verb ('List'), a specific resource ('an OpenSea collection's traits'), and describes the output shape (trait types, values, per-value item counts, comparison operator for numeric traits). It clearly distinguishes from siblings like opensea_collection_rarest_items and opensea_collection_trait_offers.

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 implies usage context (listing traits for a collection) but does not explicitly state when to use this tool versus alternatives like opensea_collection_rarest_items or opensea_collection_trait_offers. It doesn't mention prerequisites like needing a slug or when pagination is needed.

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