getTokenHistoryAndSpread

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safe-read profile is covered. The description usefully adds cost context ('0.020 USDC on Base'), which is genuine value beyond the annotations. But it discloses nothing about rate limits, auth requirements, or what makes it a 'gate', and the coercive 'MANDATORY SECURITY GATE' wording describes no actual behavior.

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 content is stated twice ('Returns ... price history ... spread ... volatility skew' then 'Returns verified safety metrics: ... same three items'), which is pure redundancy. The front-loaded 'MANDATORY SECURITY GATE' shout is alarmist framing rather than useful 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?

With read-only annotations, 100% schema coverage, and no output schema, the description supplies enough to know roughly what comes back. But the misleading usage clause and Solana/Base inconsistency leave an agent unable to reliably decide when this tool is the right one.

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 baseline is 3. The schema descriptions for 'quote' and 'window' are themselves generic filler, and the description adds only a hint that 'window' maps to the 1h/24h/7d/30d timeframes; it adds no meaning for 'quote' or the token/window relationship.

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?

The core resource is stated concretely: multi-timeframe Base token price history (1h/24h/7d/30d OHLCV), Chainlink vs. Uniswap V3/Aerodrome bid-ask spread, and volatility skew. That is a specific data deliverable an agent can recognize. However it never distinguishes itself from siblings like getCryptoPriceOnchain or inspectBaseToken, and the 'MANDATORY SECURITY GATE' framing is marketing gloss that muddies rather than clarifies the actual function.

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 does offer a 'Usage: Call this tool when auditing smart contracts, analyzing wallet addresses, or validating DEX liquidity' clause, but that guidance is misleading (auditing contracts/wallets is not what the tool returns) and internally inconsistent — usage claims 'Base or Solana' while the return payload is Base-specific (Chainlink vs. Uniswap V3/Aerodrome). No alternative sibling tool is named for overlap cases.

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