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

Annotations already declare readOnlyHint and destructiveHint=false, so the closing 'Read-only' adds nothing and is slightly redundant. It does, however, disclose genuinely useful behavior beyond the annotations: the data source is the token's deepest pool (so prices are pool-specific, not an aggregate), results are ordered oldest first, values are USD-denominated, and a summary block with drawdown/breakout metrics is returned alongside the candles.

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 what is returned and how it is ordered before explaining the summary metrics. The trailing 'Read-only' is wasted space given the annotations, but otherwise there is little filler.

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?

The description usefully covers the return payload, which matters because there is no output schema. But for a call with 0% schema coverage on four parameters and a bounded limit, omitting interval/limit/token-format guidance leaves an agent guessing on inputs it must supply.

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% across four parameters, and the description says nothing about chainId, token address format, the interval enum (5m through 1d), or the limit range of 10-300 with a default of 96. It spends its detail budget on output fields instead of compensating for the undocumented inputs, leaving interval and limit semantics unexplained anywhere.

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?

Names a specific resource and narrows it precisely: candles for one token, sourced from its deepest pool, ordered oldest first, denominated in USD. That scope distinguishes it from siblings like trending_tokens or search_tokens, though it never explicitly names an alternative.

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?

Offers an implied use case ('to judge a pullback or a breakout before buying'), which positions it as pre-trade analysis, but gives no explicit when-to-use/when-not rules and names no alternative for obtaining price data on other pools or aggregated venues.

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