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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and non-destructive. The description adds that it hits exactly one endpoint and returns that response verbatim, and that results include confidence intervals, which is modest extra context. It says nothing about pagination behavior, rate limits, or what happens for unknown feed addresses.

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 resource name, but the body is padded: 'Solana API endpoint ... on Solana' repeats itself, and the endpoint-URL sentence adds little for an agent that already knows the tool name. Three sentences deliver roughly one sentence of unique information.

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?

An output schema exists, so return values needn't be explained, and annotations cover safety. But with 6 parameters including a nested, vaguely-described resolution object and time-window parameters, the description gives no guidance on how to page, how to pick a resolution, or what the timeStart/timeEnd semantics are — leaving real gaps for a time-series tool.

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 every parameter including the nested resolution object is already documented in structured form. The description only reiterates that priceFeedAddress is part of the path, adding no interpretation value. Baseline 3 applies.

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 verb+resource: fetching historical Pyth oracle price time series, with confidence intervals, for a given price feed. That is a clear purpose. However, it never distinguishes this from close siblings get-pyth-price, get-pyth-price-candles, or list-pyth-price-feeds, so an agent must guess which to pick.

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 statement of when to use this versus get-pyth-price (spot) or get-pyth-price-candles (OHLC-style). The description lists no prerequisites, no exclusions, and no alternatives despite three obvious sibling candidates.

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