get_trending_nfts

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

Describes the return format in detail (string with 7 metrics) and notes the data source (user search behavior). Without annotations, it adequately conveys this is a read-only query, though it could explicitly state no side effects.

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?

Description is relatively concise with a logical flow: purpose, output details, use cases. The list of metrics is embedded in prose, which is acceptable but could be more scannable.

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 no annotations and empty input schema, the description provides sufficient behavioral context and output details. It covers purpose, output, and use cases, but could mention any limitation (e.g., only top 7).

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 has zero parameters, so the description does not need to explain them. The description adds value by detailing the output metrics beyond the empty 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 it retrieves the top 7 trending NFT collections based on popular user searches, with a specific verb and resource. It distinguishes from sibling tools like get_trending_coins and get_trending_categories by focusing on NFTs.

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?

Explicitly lists use cases for discovery and monitoring of NFT trends. However, it does not specify when not to use this tool or mention alternative tools for broader market trends, leaving some gap in guidance.

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