opensea: openseaGetNFTListings

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

Annotations declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true, already conveying safe and predictable behavior. The description adds that it retrieves 'active sell listings', which is consistent. However, it does not provide additional behavioral details like pagination, authentication, or rate limits, which are not required given annotations but could be improved.

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 that clearly conveys the tool's purpose without wasted words. It is front-loaded with the core action and scope.

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?

There is no output schema, and the description does not describe the return format or fields (e.g., price, maker, expiration). For a tool that returns listing data, this leaves the agent without essential context to process the response, making it incomplete.

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?

The input schema fully describes all three parameters (chainId with enum, contractAddress, tokenId) with clear descriptions. The description adds no additional semantic value beyond the schema. With 100% schema coverage, baseline is 3.

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'), resource ('active sell listings'), and scope ('for an NFT on OpenSea'). It distinguishes itself from sibling tools like openseaGetBestListings and openseaGetNFTOffers by specifying 'active sell listings'.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., openseaGetBestListings for best prices or openseaGetNFTOffers for offers). The context from the name and description implies it retrieves all active sell listings, but missing explicit usage boundaries.

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