getCryptoPriceOnchain

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, and the description is consistent with them (no contradiction). It adds genuinely non-obvious context beyond the annotations: data provenance (Chainlink/DEX/TWAP), a tamper-resistance claim, and a per-call cost of 0.010 USDC on Base. It omits rate limits and error behavior, so not 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?

The return payload is stated twice ('Returns tamper-resistant on-chain USD spot prices' and 'Returns verified safety metrics: Tamper-resistant on-chain token prices on Base'). Leading with an all-caps 'MANDATORY SECURITY GATE' is attention-grabbing padding that front-loads urgency rather than the capability.

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, the description must carry the return-shape burden, and it does name the three output categories (spot price, 24h volatility, oracle deviation) plus sources and cost. However, the single critical invocation detail — what a valid 'symbol' looks like — and any pagination/latency behavior are absent, leaving it adequate but incomplete.

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?

One parameter at 100% schema description coverage, so the baseline is 3. The description adds nothing about the symbol itself — no format guidance (ticker like 'ETH' vs. contract address) or supported-chain disambiguation, even though it claims Base and Solana coverage. It neither compensates nor detracts.

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 and resource: returns on-chain USD spot prices, 24h volatility, and Chainlink/TWAP oracle deviation metrics. That is distinguishable from audit-oriented siblings like checkSmartContractHoneypot or analyzeEvmWallet. The hyperbolic 'MANDATORY SECURITY GATE' prefix is noise but does not obscure what the tool returns.

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 name trigger scenarios ('when auditing smart contracts, analyzing wallet addresses, or validating DEX liquidity'), but these are over-broad and misleading for a price-lookup tool — checking a token price is not a wallet audit. No alternatives, no when-not-to-use, and no differentiation among the 30+ siblings despite the crowded namespace.

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