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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety and reach profile is covered. The description adds one useful scoping constraint ('NFT events only', implying fungible-token or non-event activity is excluded), but says nothing about pagination or ordering behavior, which matters for a 6-param list tool. Adequate but thin given annotations carry the rest.

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 tight sentence-fragment with the wallet scope front-loaded and the event-only constraint trailing. No waste, though it is arguably over-sparse for the parameter surface it fronts.

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 readOnlyHint covers safety. However, with six parameters and many activity siblings, the absence of any usage or filtering guidance leaves the description only minimally complete for a read tool.

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% with all six parameters documented (limit 1-100, cursor, sort_by values, identifier forms, event_types). The description adds no parameter-level detail beyond the schema. Baseline 3 is correct when the schema does the heavy lifting.

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 identifies a specific resource (a wallet's NFT marketplace activity on OpenSea) and scopes it with 'NFT events only'. This distinguishes it from collection- or item-scoped siblings like opensea_collection_activity and opensea_item_activity. It stops short of naming those alternatives explicitly, but the wallet scope is clear.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as opensea_activity or opensea_item_activity. The agent must infer the wallet-scoping use case from the description alone. With this many activity-related siblings, routing guidance is missing.

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