opensea: openseaGetMyNFTs

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

Annotations already mark the tool as read-only, idempotent, and non-destructive. The description adds that it returns 'all NFTs owned by the user', which is consistent but does not elaborate on pagination, authentication needs, or rate limits. The added value is minimal beyond annotations.

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?

Two sentences, no fluff. The first sentence states the purpose, and the second provides a crisp usage directive. Every word earns its place.

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 tool's simplicity (2 optional parameters, no output schema, clear annotations), the description is nearly complete. It omits details on return format and pagination, but the presence of the 'next' parameter implies pagination. Adequate for the complexity level.

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?

The input schema has 100% description coverage for both parameters (limit and next), so the description adds no extra meaning. The baseline score of 3 is appropriate as the schema already fully documents the parameters.

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 'Get all NFTs owned by the user on OpenSea', specifying the verb, resource, and context. It distinguishes itself from other OpenSea tools which handle listings, offers, or collection 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 explicitly says 'ALWAYS use this tool first when user asks about their NFTs or NFT collection', providing clear guidance on when to prefer it. However, it does not mention when not to use it or suggest alternative tools for other NFT queries.

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