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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered by structured data. The description adds nothing behavioral beyond that — no pagination semantics, no note about which event types are returned by default, no data-freshness or rate-limit context. With annotations doing the safety work, the description still contributes almost no extra behavioral value.

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 front-loaded sentence with no filler, and the enumeration of event types is useful. It is efficient, though arguably too terse for a 12-parameter tool.

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 annotations cover safety. But for a 12-parameter, multi-sibling tool the description omits routing guidance and does not reconcile the 'Items endpoint only' parameters with an activity endpoint, leaving the agent to infer too much.

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 the schema itself documents all 12 parameters thoroughly. The description adds no parameter meaning at all — and notably fails to clarify why several parameters (traits, min/max price, rarity, listed_only) are marked 'Items endpoint only' on an activity tool. Baseline 3 for a fully-covered schema.

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 clear verb+resource ('collection marketplace activity') and enumerates the event categories returned (sales, listings, offers, transfers, mints). However, it does not differentiate from close siblings like opensea_activity, opensea_collection_top_sales, or opensea_item_activity, so an agent must infer scope on its own.

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 is given. It never says when to prefer this tool over opensea_activity, opensea_collection_offers, or opensea_collection_top_sales, nor does it note any prerequisites such as requiring a valid collection slug.

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