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

Annotations already declare readOnlyHint=true, idempotentHint=true, non-destructive, so the safety profile is covered. The description usefully notes it is a thin passthrough of a single GET endpoint and that data comes from vetted DEX pools, but says nothing about pagination behavior, default fill behavior, or timestamp/response shape that an agent might trip over.

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 with the endpoint, but the first sentence restates the title and the third sentence ('Returns clean price data from vetted DEX pools and markets') is marketing filler that does not help invocation. Tightening would leave one useful sentence about the underlying endpoint plus one about data source.

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 an output schema and full parameter coverage, the description need only establish scope and origin, which it does. The remaining gap is sibling routing against the three other candle-related tools, which is the one thing structured fields cannot 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 100%, including the marketAddress path parameter and the detailed fillEmptyCandles semantics, so the schema carries the parameter burden. The description adds no parameter syntax, units, or default information beyond what is already structured.

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: fetches OHLCV candlestick data for a specific Solana market/pool via a named endpoint. The market/pool scoping implicitly distinguishes it from get-token-candles and get-pyth-price-candles, but it never names those siblings explicitly, so the differentiation is left to inference.

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?

No guidance on when to use this over get-token-candles or get-pyth-price-candles, which return similar candle data for different asset scopes. It also lacks any prerequisite or exclusion (e.g. which markets are supported, whether price data is needed instead of token candles). Usage is only implied by the resource name.

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