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 useful behavioral detail that offers are 'standing' and returned 'grouped by price level,' but says nothing about authentication, rate limits, or pagination behavior beyond what the schema provides.

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, front-loaded with purpose and followed by the routing alternative. Every clause earns its place with no filler.

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, rich parameter descriptions, and annotations covering the read-only/open-world profile, the description supplies the purpose and sibling routing an agent needs. It could be more complete by clarifying parameter applicability (many schema fields are labeled 'Items endpoint only'), but the structured fields carry most of the load.

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% across 12 parameters, so the schema already documents every field. The description adds no parameter-level meaning (e.g., which traits format to use or that only a subset of params apply to this endpoint), making the baseline 3 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?

States a specific verb (Fetch) and resource (OpenSea standing offer rows for one collection trait value), plus the aggregation scope (grouped by price level). It explicitly distinguishes itself from the collection-wide sibling opensea_collection_offers, so an agent can route correctly without opening schemas.

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?

Names an alternative (opensea_collection_offers) and the condition that selects it (collection-wide offer book), which is the key routing decision. It does not mention other nearby siblings such as opensea_item_offers or explicitly state when not to use this tool, so it falls short of fully exhaustive guidance.

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