Solana: getPumpFunTokens

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

Annotations already provide safety cues (readOnlyHint=true, idempotentHint=true). The description adds only the token categories, which are in the schema enum, and does not disclose response format, pagination, or other behaviors.

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?

Single short sentence with no wasted words. Front-loaded with the main purpose.

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?

Despite high tool complexity (25 parameters, no output schema), the description provides insufficient context. It does not explain usage, filtering, or return values, leaving the agent underinformed.

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 description coverage is 32% (low), yet the description adds no parameter explanations. For 25 parameters, the description should compensate, but it does not.

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?

Clearly states 'Query PumpFun tokens' with three categories, fulfilling verb+resource. However, it does not differentiate from sibling tools like birdeyeTrendingTokens or findSolanaGems, which also query tokens.

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?

No guidance on when to use this tool versus alternatives such as baseFindClankerTokens or findSolanaGems. The description lacks usage context or exclusions.

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