get_token_price

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

Annotations provide readOnlyHint, idempotentHint, openWorldHint. Description adds that it's a snapshot, EVM-only, and includes agent behavior constraints (not a pick tool). No contradictions.

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?

Well-structured and informative, but includes a minor reference to 'Issue #599' that adds little value. Otherwise clear and efficient.

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?

Covers input, alternatives, and scope well. Lacks explicit output format (e.g., number or object), but states it returns current spot USD price. Sufficient for a simple 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?

With 0% schema coverage, description explains 'native' vs contract address for token parameter and lists supported chains in schema. Adds examples for native assets per chain.

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?

Description clearly states it fetches USD price via DefiLlama, specifies token as 'native' or ERC-20 address, and distinguishes from siblings (get_swap_quote for swaps, get_coin_price for non-EVM natives).

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?

Explicitly says when to prefer this tool over get_swap_quote and when to use get_coin_price for non-EVM natives. Also clarifies scope: current spot price, not a forecast or signal.

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