Recent sales

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

Annotations already cover the safe-read (readOnlyHint) and external-fetch (openWorldHint) profile, so the bar is lower. The description adds real context beyond them: data is sourced from multiple marketplaces and OpenSea results are conditionally merged depending on readability and slug availability.

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?

Three sentences, front-loaded with the core operation and output fields, followed by accepted identifiers and the conditional OpenSea behavior. No filler; slightly dense in the second half but every clause carries information.

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 no output schema, the description takes on the burden of describing returns and does so (price, buyer, seller, tx signature) while 'most recent' implies ordering. Some detail such as pagination behavior or exact ordering tie-breaks is absent, but the definition is sufficient for correct invocation.

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 coverage is only 33% (only 'limit' is documented), so the description must compensate, and it does: it explains that 'collection' accepts a registry id or Magic Eden symbol and clarifies the role of 'openseaSlug' as an optional override. The 'limit' parameter is left to the schema, which is acceptable.

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+resource ('Most recent completed sales for a collection') and enumerates returned fields (price in SOL, buyer, seller, tx signature), plus the cross-marketplace scope. It does not, however, distinguish itself from the closely named sibling get_collection_sales, which appears to describe a similar resource.

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?

Usage is only implied: it explains that OpenSea sales are included 'when OpenSea can be read and a slug is known,' which tells the agent about conditional behavior but not when to prefer this over get_collection_sales. No exclusions or explicit alternative-routing are given.

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