get_token_price

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

With no annotations provided, the description must fully disclose behavioral traits. It mentions the revert condition (PriceFeedNotFound) but does not detail the return format (e.g., price as number or string, age as timestamp or duration), potential latency, or whether modification occurs. It adds some value but lacks completeness.

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 long, directly stating the core function and a key error condition. It is front-loaded, with no extraneous information, making it efficient for an agent to parse.

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?

Given the tool's simplicity (one parameter, no output schema) and the absence of annotations, the description covers the basics but omits details like return value format (e.g., price is a float, age in seconds) and whether the price is scaled. This leaves some gaps for an agent to infer.

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?

The schema provides 100% coverage for the single parameter 'token' with a clear description ('Token contract address'). The description does not add further semantics beyond what the schema already conveys, so the baseline of 3 is appropriate.

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 clearly states the tool returns the USD price of a token via the PriceFeedRegistry, including the feed's age. It also specifies an error condition (reverts for unregistered tokens and all Stock Tokens), which distinguishes it from sibling tools like get_stock_price.

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 implicitly guides usage by stating it reverts for Stock Tokens, indicating that such tokens should be handled by a different tool. However, it does not explicitly state when to use this tool over alternatives like read_price_feed or list_price_feeds, leaving some ambiguity.

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