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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds genuinely new behavioral context: this is a paid endpoint costing 0.020 USDC payable on Base or Solana, which an agent must know before invoking. It does not disclose latency, rate limits, or failure modes, keeping it below a 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?

A single front-loaded sentence that packs the three output categories first and the payment terms last, with no filler. It is dense but every clause carries information an agent needs; a short clause on window/quote would have been a better use of space than nothing.

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-shape detail is rightly omitted, and the payment requirement is a valuable addition. However, with 3 parameters at 33% schema coverage and no required fields, the description leaves the semantics of 'window' and 'quote' (and their defaults) unclear, which is a real gap for a parameterized 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 coverage is only 33% — only 'token' is documented ('symbol or Base contract address'), and the description reinforces the Base-token scope. The four timeframes (1h/24h/7d/30d) hint at the 'window' parameter's accepted values but also read as returned data, leaving it ambiguous whether window selects a timeframe or the response always contains all four; 'quote' is never explained.

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 ('Returns') and enumerates the exact resources produced: multi-timeframe Base token OHLCV, Chainlink vs. Uniswap V3/Aerodrome spread in bps, and realized volatility skew. This is detailed enough to separate it from siblings like getCryptoPriceOnchain (single price) or inspectBaseToken (token metadata) without opening any schema.

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?

There is no explicit when-to-use statement and no named alternative, so the agent must infer from the output inventory that this is the tool for spread/volatility analysis on Base. The listed outputs imply the use case but no exclusions or routing guidance are given.

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