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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safe read-only nature is covered. The description adds that results are 'standing' (active) rather than historical, which is genuinely useful context, but it says nothing about pagination behavior despite a cursor param, nor about result freshness.

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 short sentence with the key qualifier front-loaded and zero waste. It is efficiently structured, though arguably so terse that it leaves obvious questions unaddressed.

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?

With an output schema present, the description needn't explain return values, and annotations carry the safety profile. However, for a 3-required-param paginated listing tool that competes with many opensea_item_* siblings, the absence of any routing or usage context leaves it only minimally 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 every parameter (chain, contract_address, token_id, limit, cursor, event_types, sort_direction) is already documented in the schema. The description adds no additional semantics for any parameter, so the baseline 3 applies.

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 resource ('standing sell orders') scoped to one NFT, and the word 'standing' usefully distinguishes live listings from historical sales or offers. It never names the sibling it contrasts with (e.g. opensea_item_offers for buy-side orders), so it is clear but not sibling-differentiated.

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, no prerequisites (chain/contract/token are required but that is only in the schema), and no mention of the alternatives like opensea_item_offers or opensea_item_activity. The agent must infer the selection criteria entirely from the title.

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