opensea: openseaGetMyNFTs

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=true, so the agent knows the tool is safe and read-only. The description adds behavioral context ('Get all NFTs owned by the user') and a strong usage hint, which goes beyond what annotations provide. No contradictions.

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 consists of two concise sentences. The first states the purpose, and the second provides a critical usage guideline. Every sentence adds value without redundancy.

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, the description adequately covers purpose and usage context. Annotations and schema cover safety and parameters. The tool lacks an output schema, but returning NFTs is implied. Slight gap: could mention pagination, but schema handles it.

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?

Input schema coverage is 100% with both parameters ('limit' and 'next') described. The description does not add parameter-specific information, but per guidelines, baseline is 3 when coverage is high. The description does not harm or add to parameter understanding.

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', using a specific verb ('Get') and resource ('NFTs owned by the user'). It also distinguishes itself from siblings by providing a usage directive: 'ALWAYS use this tool first when user asks about their NFTs or NFT collection.'

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 tells when to use this tool ('ALWAYS use this tool first when user asks about their NFTs or NFT collection'), but does not specify when not to use it or mention alternative tools. This provides clear context but lacks exclusions.

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