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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the agent knows this is a safe read operation. The description adds a hint about pagination via nextPageId, which is useful, but it does not disclose return format or other behavioral traits beyond what annotations already provide.

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 short sentences, front-loaded with the purpose and then a pagination hint. There is zero wasted text; every sentence contributes meaning.

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?

For a tool with 6 parameters, no output schema, and many sibling token tools, the description is severely under-specified. It provides a basic pagination pattern but omits critical details like valid sort values, platformId semantics, and return structure, making it insufficient for reliable invocation.

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 compensate for all parameters. It explains 'size' (pass size=5) and 'nextPageId' (paginate), but leaves 'sort', 'mintType', 'platformId', and 'includeNsfw' completely unexplained, including the required 'sort' parameter.

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 'Get LaunchLab / bonk.fun tokens' uses a specific verb and resource, making the purpose immediately clear. It also distinguishes this tool from sibling token tools like getPumpFunTokens or findSolanaGems by naming the LaunchLab 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 implies usage for LaunchLab/bonk.fun token discovery, which is a clear context, but it provides no explicit when-to-use instructions or alternative comparisons. It lacks guidance on when to prefer this over sibling tools, so it falls short of a 4.

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