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

Consistent with readOnlyHint/idempotentHint and adds genuinely load-bearing context the annotations cannot express: the endpoint is Pro-tier-only, the platform key will fail, and the response shape is unverified. That last admission is unusually honest and prevents an agent from over-trusting the return fields. It omits rate-limit or pagination-termination behavior, keeping it below 5.

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?

The purpose leads, then caveats follow in a logical order. The Solscan announcement date is arguably dead weight, but every other clause carries operational information, and there is no filler or repetition.

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 and a nested extra_params object, the description does the right things: it flags that the response shape is unverified and that certain parameters must be discovered from Solscan's own docs. The main remaining gap is expected return structure and paging semantics, but that gap is explicitly acknowledged rather than hidden.

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 the schema already documents cursor, time_from/time_to, time_bucket and pool_address; baseline is 3. The description only reinforces the bucket range and clarifies that extra_params is forwarded verbatim — marginal but real added 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?

States a specific verb+resource: OHLCV price candles for a Solana liquidity pool, with bucket granularity (1m–1y) and cursor paging. It is unambiguous what the tool returns, though it never names or contrasts a sibling such as get_dex_activity or get_token_screener, so the agent must infer the boundary.

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 a hard precondition (Pro-tier Solscan key required; the platform Free-tier key cannot call this) and an escape hatch (use extra_params for fields not covered). What it lacks is any when-to-use-this-vs-something-else guidance among the many market-data siblings.

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