opensea: openseaGetCollectionActivity

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

Annotations already provide readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=true. The description adds marginal behavioral context (monitors activity) but does not disclose additional traits such as rate limits, data freshness, or behavior when no activity exists.

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?

The description is two sentences, both front-loaded: first states purpose and examples, second suggests use case. No redundant or unnecessary 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?

No output schema exists, and the description does not explain the return format (e.g., structure of event objects, pagination details). For an activity monitoring tool with 4 parameters, the agent lacks information to interpret results, making it incomplete.

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?

With 100% schema coverage, the baseline is 3. The description lists event types but does not add new semantic meaning beyond the schema's parameter descriptions (e.g., collectionSlug, eventType, limit, next).

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?

The description clearly states the tool's purpose: monitoring recent activity for an NFT collection, listing specific event types (sales, transfers, mints, listings, offers). This distinguishes it from sibling tools like openseaGetBestListings (focuses on listings) and openseaGetCollectionStats (aggregate stats).

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?

The description indicates general usage ('track market activity and recent trades') but does not explicitly specify when to use this tool over alternatives or when not to use it. No guidance on prerequisites or exclusions is provided.

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