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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the read-only, live-data nature is covered. The description adds that output is aggregated into price levels with quantities, which is real behavioral context. It does not mention freshness, rate limits, or that levels may be empty, so it clears but does not exceed the lower bar.

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 first two sentences are front-loaded and earn their place, but the three parameter sentences restate the schema verbatim and consume roughly half the text, diluting an otherwise tight definition.

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 the description still characterizes the shape of the ladder. With annotations handling the safety profile and a fully documented schema, the only missing piece an agent needs is any caveat about empty or stale ladders.

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% and the description's parameter notes ('chain: Chain identifier, for example ethereum. Required.') merely repeat the schema verbatim, adding no format or validation detail. Baseline 3 applies when the schema does all the work.

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 and resource ('Returns the bid/ask ladder for a single NFT'), then defines exactly what a ladder contains (resting listings and offers grouped into price levels with quantity). This distinguishes it from opensea_item_offers and opensea_collection_depth without opening a schema.

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?

It names a concrete use case ('Useful for ERC-1155 items where many units trade at different prices') and points to opensea_item_offers as the alternative for plain standing offers. It does not state when NOT to use it (e.g., ERC-721 single-unit items where a ladder is trivial), but the routing is largely explicit.

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