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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower; the description adds meaningful output behavior: it returns indexed metadata, a page link, recent trades, top holders, and a top-10-concentration rug-flag. No contradiction with 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 dense sentences front-load the purpose and delimit scope, then enumerate output categories and usage context. No filler or repetition of schema details.

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 read-only single-token retrieval with rich annotations and complete schema descriptions, the description covers what the tool returns, how to source the address, and its place in the workflow. The absence of an output schema is compensated by enumerating the output groups.

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%, so the baseline applies: parameters (token_address, chain_id, trades_limit, holders_limit) are already documented with defaults and chain tie-break details. The description only loosely maps 'recent trades and top holders' to the limit params and adds little parameter-specific meaning.

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 names a concrete operation ('get token by address') and clearly delimits scope to ONE launchpad token, enumerating the returned metadata categories. This distinguishes it from sibling tools like launchpad_list_tokens, which covers the full set.

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?

It gives explicit invocation context: use after launchpad_list_tokens or with a launch-receipt address. It does not spell out 'when not to use' compared with all other launchpad siblings, but the singular-vs-list contrast and sequencing make the intended workflow clear.

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