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

Read-only and open-world hints are already in annotations, and the description still adds real behavior: cursor pagination, the contents of each item (collection/rarity/best listing), and the extra lookup cost for ENS/username identifiers. It does not describe rate limits or response envelope details, but with annotations covering safety this is solid.

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 core purpose and pagination note are front-loaded and useful, but a large chunk of the description is verbatim parameter repetition that duplicates the schema and at times contradicts this tool's scope. Trimming the param echo would sharpen it.

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?

For a read-only paginated list with a rich output schema and 100% schema coverage, the description covers purpose, identifier semantics, pagination, and one sibling alternative. Return-value details are rightly left to the output schema; only coverage of the other opensea_profile_* siblings is missing.

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% and an output schema exists, so the schema carries the parameters. The description largely restates schema text (limit range/default) and some of its param notes appear copied from other tools ('Activity only', 'Created-collections only'), which adds confusion rather than value. Baseline 3 applies.

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 a cursor-paginated page of NFTs held by a wallet, including collection, rarity rank, and best listing. It distinguishes itself from opensea_profile_created by name. However, embedded param text (event_types 'Activity only', sort_by 'Created-collections only') references sibling scopes and muddies what this tool actually returns.

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 one explicit routing rule: use opensea_profile_created to list collections a wallet created, and notes that a non-address identifier costs one extra resolution lookup. It stops short of covering the other close siblings (profile_collections, profile_activity), so no full when-not guidance.

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