Solana: discoverLaunchLabTokens

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true, fully covering behavioral safety. The description adds pagination details (nextPageId) but does not disclose additional traits beyond what annotations provide. No contradictions.

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 concise (one sentence), but it omits critical parameter details, making it too sparse. Every sentence should add value; here, the brevity sacrifices completeness.

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 6 parameters, no output schema, and only a minimal description, the tool definition is incomplete. It fails to explain return values, the meaning of most parameters, or full pagination behavior. For a complex tool, more context is needed.

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 0%, so the description must explain parameters. It only mentions 'size' and 'nextPageId' for pagination, leaving 'sort', 'mintType', 'includeNsfw', and 'platformId' unexplained. This insufficiently compensates for the schema's lack of descriptions.

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 title and description explicitly state 'Get LaunchLab / bonk.fun tokens', which clearly identifies the specific resource and action. It differentiates from sibling tools like 'getPumpFunTokens' by naming a distinct token platform.

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 a usage hint about pagination ('Pass size=5, paginate with nextPageId'), but does not specify when to use this tool versus alternatives like 'getPumpFunTokens' or other token discovery tools. Context signals show many siblings, yet no guidance on selection.

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