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

Annotations already declare readOnly/openWorld/idempotent/destructive=false, so safety is covered. The description adds real behavioral context beyond that: it composes two promoted-token endpoints plus per-token pool detail, and notes it checks up to 30 candidate tokens per call, which signals a hidden ceiling an agent would otherwise miss. It stops short of describing failure behavior or rate limits.

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?

Front-loaded and largely informative, but repetitive: 'new/trending' is scare-quoted three times and the same homepage-surfaces concept is restated in both the middle and end. The 'same data as get_token' parenthetical and the closing repetition could be trimmed without losing 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?

With no output schema, the description compensates by enumerating the returned fields (price, liquidity USD, 24h volume, market cap/FDV, pool creation time) and the candidate cap. Combined with the usage examples, an agent has everything needed to call and interpret it.

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 100%, so enums, defaults, and ranges for all six parameters are already documented. The description only gestures at filters ('by liquidity, volume and market cap') and adds no syntax or default detail beyond the schema. Baseline 3 is correct when the schema carries the semantics.

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?

States a specific verb+resource (filterable screen for new/trending tokens) and explicitly differentiates from siblings by naming latest_token_profiles, latest_boosted_tokens, and get_token as its data sources. An agent can distinguish it from those sibling tools without opening their schemas.

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?

Gives concrete example queries ('trending solana memecoins with liquidity over $1000 and market cap under $1M'), states the explicit exclusion ('NOT DEX Screener's full new-pair firehose'), and clarifies the exact surface it screens. The when-to-use condition and the alternative surface are both spelled out.

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