opensea: openseaGetNFTOffers

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

Although annotations (readOnlyHint, idempotentHint) already declare it as a safe read operation, the description does not add any behavioral traits beyond the one-line summary. It fails to mention potential limitations such as rate limits, authorization requirements, or pagination.

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 a single concise sentence (5 words) with no unnecessary content. It is front-loaded and efficient.

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?

Despite good annotations, the description lacks completeness for a tool that retrieves offers. It does not mention what data is returned (e.g., price, expiration) or any constraints (e.g., only active offers). With no output schema, more context would be beneficial.

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% with descriptions for all parameters (chainId enum, contractAddress, tokenId). The description does not add extra meaning beyond what the schema already provides, so a baseline of 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 clearly states the action 'Get' and the specific resource 'buy offers for an NFT on OpenSea'. It distinguishes itself from sibling tools like 'openseaGetBestListings' and 'openseaGetNFTListings' by focusing on buy 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 provides no guidance on when to use this tool versus other similar tools (e.g., openseaGetBestListings for best offers, openseaGetNFTListings for all listings). It lacks exclusion criteria or contextual hints.

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