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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds no behavioral context beyond that—no auth requirements, no rate limits, and no indication of how results are ordered or paginated, despite the schema containing those controls.

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?

It is a single terse sentence fragment with no wasted words, but it is under-specified rather than appropriately concise for a six-parameter tool. There is no front-loading of purpose, scope, or routing guidance.

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?

Given the output schema exists, return values need not be explained, and annotations cover safety. But with six parameters and many sibling profile/collection item tools, the description omits any routing or scope context, leaving the agent to infer whether this returns owned versus created items.

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% for all six parameters, so the schema already documents identifier, limit, cursor, sort_by, sort_direction, and event_types. The description adds no parameter meaning beyond what the schema provides; the baseline of 3 applies 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 fragment names the resource (NFTs) and scope (held by an OpenSea wallet), so an agent can infer it returns owned NFTs. However, it lacks a verb and does not differentiate from sibling tools like opensea_profile_created or opensea_collection_items, so selection still requires inference.

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, no prerequisites, and no alternatives are named. The description gives no signal about when this endpoint should be chosen over other profile or collection item endpoints.

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