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

Annotations already declare readOnlyHint/idempotentHint, and the trailing 'Read-only' merely repeats them. The description earns credit elsewhere: it names the authoritative data source (the Flaunch pool indexer), the denomination (ETH with a per-candle ETH/USD rate), and the data-window limits per interval — all traits an agent cannot get from 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, with the primary content (what is returned) front-loaded and the interval table compressed into one clause. The final 'Read-only' is redundant with the annotations and is the only wasted fragment.

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 carries the return-shape burden and does so adequately: it discloses both data families (candles, recent trades), the denomination, and the per-interval windows. Minor gaps remain around candle count/pagination limits and trade ordering, but nothing that would cause a mis-call.

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 is 3; the description exceeds it by explaining what each interval actually returns in terms of lookback horizon and by clarifying that candle values are in ETH with an accompanying ETH/USD rate. The 'trades' parameter is left to the schema, which is acceptable given its documented default and maximum.

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 concrete resource (OHLC candles plus recent trades for a CoinFactory-launched token) and specifies the data source (CoinFactory's own indexer of its Flaunch pool), which is more specific than the sibling names suggest. It does not explicitly contrast itself with get_market_data or get_launched_token, so an agent must infer the boundary from the word 'launched'.

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 interval-to-lookback mapping (5m = last 24h, 1h = 14 days, 1d = 1 year) gives practical guidance on which interval to pick for a desired window. However, there is no statement of when to use this tool versus get_market_data, get_launched_token, or get_trending, and no prerequisites or exclusions.

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