get_token_price

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

Explains the on-chain derivation (token price × native token USD price), providing insight into how the price is computed. No annotations exist, so description covers behavioral aspects well. Could note that price may be delayed or require specific chain state.

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?

Two sentences, front-loaded with main purpose, no unnecessary words. Highly concise while covering key details.

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 could mention the return format (e.g., float in USD). However, the tool name and description imply a numeric price. Adequate for a simple lookup 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 covers all three parameters with descriptions. Description adds value: explains token accepts symbol or address, chain accepts aliases, and version omission uses highest-volume. Enhances understanding beyond schema.

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?

Clearly states it returns the current USD price of a token on Uniswap. Specifies inputs (symbol or address) and mentions the derivation method. Distinct from siblings like pool_info or list_markets.

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?

Describes accepted inputs (symbol/address, chain, optional version) and gives a sanity-check tip. Does not explicitly contrast with siblings, but the purpose is clear enough that this is the price lookup tool.

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