Solana: findSolanaGems

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds context on the types of tokens and stocks returned, and the categories. It could mention pagination or rate limits, but overall adds significant behavioral context beyond 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?

Two paragraphs efficiently covering purpose, categories, usage examples, and exclusions. Every sentence adds value, no 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 covers purpose, usage, and filtering scope. It lacks details on return format or how filters combine, but is sufficient for a discovery 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?

Schema coverage is 100% with many parameters having enums and descriptions. The description adds extra meaning for 'category' and 'sortBy' (e.g., sortBy only applies to tokens). Other parameters like liquidity and market cap filters are not elaborated, but the core parameters are well explained.

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 subcategories for 'tokens' and 'stocks'. It distinguishes from siblings like findSolanaSwapToken and getPumpFunTokens by explicitly stating what it is NOT for.

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?

Provides explicit examples of when to use (e.g., 'trending tokens', 'find gems', 'show stocks on solana') and when not to use ('specific token lookup', 'PumpFun queries'), naming alternative tools.

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