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. 'Standing bids' adds a small semantic cue that these are active offers rather than historical events, but nothing is said about pagination behavior, sorting, or freshness despite a cursor/limit/sort_direction schema.

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 six-word fragment with zero redundancy, and the key scope ('one OpenSea NFT') is front-loaded. It is efficient, though the extreme brevity comes at the cost of the other dimensions.

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 explained, and annotations cover the safety profile. Still, for a 7-parameter paginated query the description says nothing about the required chain/contract/token identity trio or paging, leaving it minimally viable rather than 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 all seven parameters are already documented in the schema. The description adds no parameter meaning beyond that, which is the expected baseline when the schema does the heavy lifting.

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 phrase 'Standing bids on one OpenSea NFT' names the resource (offers/bids) and scope (one NFT), which does distinguish it from the listings/asks sibling. However, it is a noun fragment with no verb, so it never states that the tool lists or retrieves offers, leaving the agent to infer the operation.

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?

There is no when-to-use guidance at all. With siblings like opensea_collection_offers, opensea_collection_trait_offers, opensea_item_listings, and opensea_item_activity, the description should say when item-level offers are preferable to collection-level offers or listings, but it does not.

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