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

The word 'realized' adds genuine behavioral meaning — only completed sales, not listings or offers. Beyond that, nothing is said about time range, granularity, currency, or pagination. With readOnlyHint and openWorldHint already covering the safety profile, this is adequate but thin.

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?

One front-loaded sentence with no filler; the identity of the resource is stated immediately. It is efficient, though its brevity comes at the cost of any usage or behavior detail.

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-value shape need not be described. However, for a historical time-series tool the agent would benefit from knowing the default lookback window or granularity, which is absent.

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?

All three parameters (chain, contract_address, token_id) are fully described in the schema at 100% coverage, so the description is not obliged to explain them. It adds nothing beyond the schema's own field docs, which matches the baseline.

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 and data type: realized sale-price history for a single OpenSea NFT. 'Realized' usefully distinguishes it from listing/offer-style siblings such as opensea_item_listings or opensea_item_offers, though it never names those siblings explicitly.

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 when-to-use guidance, no mention of alternatives (e.g. opensea_item_activity or opensea_collection_chart), and no prerequisites stated. The agent must infer usage purely from the one-line purpose.

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