list_nfts

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

Since no annotations are provided, the description carries the full burden. It states that it is a listing operation returning an array of NFT collections with specific fields. However, it does not disclose rate limits, authentication needs, or error handling, which would be helpful.

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 is very concise with a clear purpose sentence, followed by structured Args and Returns sections. No wasted words.

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 listing tool with 3 parameters and no output schema, the description provides acceptable information: sort options, pagination, and return fields. It directs to 'get_nft_collection' for details. Could be improved by noting default sort direction.

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 descriptions of parameters are minimal ('Sort order', '1..250', 'Page number'), but the purpose text adds meaning by listing sortable metrics. Schema coverage is 0%, so the description partially compensates but does not explain all enum values.

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 the tool lists NFT collections with sort options (floor price, market cap, 24h volume). It distinguishes from sibling 'get_nft_collection' which is for a single 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 explains the sort, pagination, and return fields. It directs to 'get_nft_collection' for details, providing an alternative. However, it does not explicitly state when not to use this tool or compare to other listing tools.

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