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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds a genuine behavioral detail not in annotations: delisted or blacklisted collections return 404. It omits auth/rate-limit behavior, but adds real error-case context beyond the structured data.

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: the purpose and returned fields come first, followed by error behavior and sibling routing. Zero filler, well front-loaded.

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 explained, and annotations cover the safety profile. The description covers purpose, error behavior, and alternatives. It could note any pagination or rate limits, but is complete enough to invoke 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% and the single slug parameter is fully documented in the schema, so the schema does the heavy lifting. The description references `slug` and points to opensea_search_collections for slug discovery, which is marginal added value. Baseline 3 is appropriate here.

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 (Fetch) and resource (OpenSea collection metadata and trading-stat records) and enumerates the concrete fields returned (verification, contract/chain, floor, top offer, rolling sales/volume/floor changes). This clearly distinguishes it from sibling tools like opensea_collection_items or opensea_item.

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?

Explicitly names three alternatives with their selecting conditions: opensea_collection_chart for history, opensea_collection_activity for transactions, and opensea_search_collections to discover slugs. The agent has a clear routing rule without needing to infer.

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