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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and open-world scope are covered. The description adds the event taxonomy and the fields returned (counterparties, price, transaction hash), but that overlaps the output schema and it says nothing about pagination or limits. With annotations carrying the safety profile, a 3 is appropriate.

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?

Well front-loaded: purpose, then the filter example, then the alternative. However, the sentences 'chain: Chain identifier, for example ethereum. Required.' and 'contract_address: NFT contract address. Required.' are verbatim repeats of schema descriptions that do not earn their place at 100% coverage.

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 read-only/open-world behavior is covered by annotations. The description covers the required identifiers, the event filter, and the sibling alternative; only limit/cursor pagination is left to the schema, which documents it adequately.

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 100%, so the baseline is 3. The description exceeds it by showing how event_types values combine ('SALE,TRANSFER for an ownership trail'), a semantic not present in the schema's allowed-values list. It also restates chain and contract_address, which duplicates the schema rather than adding to it.

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 marketplace event history for a single NFT'), enumerates the event types covered, and names the sibling opensea_activity as the marketplace-wide alternative. An agent can tell it apart from opensea_activity and opensea_collection_activity 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?

Gives a concrete usage path ('Filter with event_types, for example event_types=SALE,TRANSFER for an ownership trail') and routes the agent to opensea_activity for marketplace-wide activity. Clear context and an alternative, though it does not spell out when-not conditions beyond that one alternative.

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