coingecko_nfts

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It states the source (public website) and normalization, but does not discuss pagination behavior, data freshness, rate limits, or that the operation is read-only (though implied). The description is too sparse for a tool with no 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?

The description is very concise with two sentences and no redundant information. However, it could be slightly more informative without becoming verbose, so it's efficient but leaves some gaps.

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?

With no output schema, the description fails to describe the return format or fields of the normalized rows. Given the presence of multiple NFT-related sibling tools, the description should clarify what distinguishes this tool (e.g., lists of collections vs market data). The current description is incomplete for an agent to fully understand the output.

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%, so baseline is 3. The description adds minimal value by noting that vs_currency supports a documented enum, but does not elaborate on the parameter meanings beyond what the schema provides. The page and limit parameters are already clear in the schema.

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 that the tool returns normalized NFT collection rows from CoinGecko's public website, using a specific verb and resource. However, it does not differentiate from sibling tools like coingecko_nft_category, which is a related but distinct tool.

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 mentions that vs_currency supports a documented enum, but provides no guidance on when to use this tool versus alternatives, nor does it specify when not to use it. There is no mention of prerequisites or context.

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