opensea_item_listings

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

With no annotations, the description carries the behavioral burden. It adds useful edge-case behavior ('an item with no active listings returns an empty list rather than a 404') and explains what each returned listing contains. It does not mention pagination or sorting behavior, but the read-only nature is strongly implied by 'List.'

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 two sentences with no filler. The first sentence states the operation and the second covers return contents plus a key edge case. Every sentence earns its place.

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?

The description is solid for a read-only list tool: it names the resource, the returned fields, and the empty-list behavior. However, it says 'every standing sell order' while exposing limit and cursor parameters, and there is no output schema, so pagination semantics are left for the agent to infer.

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 the input schema already documents all six parameters. The description adds only high-level context about OpenSea NFTs and sell orders, not per-parameter meaning. The baseline of 3 is therefore 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 opens with a concrete verb and resource: 'List standing listings for an OpenSea NFT.' It further specifies that these are standing sell orders and enumerates the returned fields, which clearly distinguishes it from related sibling tools like opensea_item_offers or opensea_item_activity.

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 use case is implied clearly: call this when you need active sell listings for one specific NFT. However, the description gives no explicit guidance about when not to use it or which alternative sibling tool to choose, so usage guidance is helpful but not fully explicit.

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