Solana: findSolanaGems

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description's job is to add context. It explains the two category modes and the nature of results (trending, popular, top traded, etc.). This adds value beyond annotations, though no additional behavioral traits like rate limits are mentioned.

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 two sentences plus a brief list of use cases and exclusions. It is front-loaded with the core purpose and immediately clarifies scope. Every sentence contributes meaning 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 complexity (16 parameters, no output schema), the description effectively conveys purpose, usage context, and exclusions. It covers the two category modes and example queries. While return format is not described, the behavioral transparency and guidelines are strong enough for most agents to understand when and how to invoke the tool.

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 16 parameters with 100% description coverage, so the schema already documents each parameter. The description adds context for the 'category' parameter but does not significantly enhance understanding of other parameters beyond what the schema provides. Baseline 3 is appropriate.

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 discovers trending Solana tokens or tokenized stocks, with specific examples for each category. It distinguishes between 'tokens' and 'stocks' and explicitly mentions what not to use it for, referencing sibling tools like findSolanaSwapToken and getPumpFunTokens.

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 provides explicit when-to-use scenarios (e.g., 'trending tokens', 'find gems', 'TSLA stock token') and when-not-to-use (specific token lookup or PumpFun queries), with direct references to alternative tools. This is excellent guidance for an AI agent.

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