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

No annotations are provided, so the description carries the full transparency burden. It discloses the cost ('Costs 0.01 USDC on Base'), the real-time nature, and the default chain. However, it doesn't mention error behavior, rate limits, or what happens for invalid addresses/symbols, keeping it at a moderate level.

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 description is two sentences with no filler. The first sentence states the purpose, and the second covers inputs, chain options, default, and cost—every word adds value.

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?

The description covers purpose, input methods, chain list, default, and cost. It implies the return value is a USDC-denominated spot price, which is sufficient given the lack of an output schema. It could mention edge cases or restrictions, but overall it's adequately complete for a simple price lookup.

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?

With 0% schema description coverage, the description compensates by explaining all three parameters: address (0x...), symbol (with specific examples), and chain (with a list and default). It implies address and symbol are alternatives via 'or,' but doesn't explicitly state mutual exclusivity, which is a minor gap.

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 description opens with a clear verb ('provide') and identifies the resource: 'real-time USDC-denominated spot price for an EVM token by contract address or common symbol.' It easily distinguishes from sibling tools like fetch_url or wallet_balance, which are unrelated.

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?

The description explicitly instructs how to use the tool: 'Provide address (0x...) or symbol (ETH, USDC, USDT, WETH) and optional chain (base, ethereum, polygon, arbitrum, optimism, avalanche, default base).' It implies when to use it (whenever a token price is needed) and lists chain options, though it doesn't name alternative tools since siblings are clearly unrelated.

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