get_token_price

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It lacks details about potential issues like API rate limits, caching behavior, or what happens if the token price is unavailable. For a tool that fetches external data, these are important considerations.

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 a single, well-structured sentence that conveys all essential information. There is no wasted text, and every word contributes to the tool's purpose.

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?

For a tool with only three parameters and no output schema, the description is adequate but not complete. It fails to explain what the return value looks like (e.g., a number, a JSON object) or any error handling behavior. A more complete description would mention the expected response format.

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 input schema provides full descriptions for all three parameters, including enum values and defaults. The description does not add any additional meaning beyond the schema, so a baseline score 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's purpose: getting live USD prices for specific tokens from CoinGecko. The verb 'Get' is specific, and the resource 'live USD price' with a defined list of tokens makes the purpose unambiguous. It naturally distinguishes from sibling tools which handle transactions or balances.

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 tells when to use this tool: whenever a live price of PHRS, USDC, USDT, or WETH is needed. Since no sibling tool provides similar functionality, there is no need to specify exclusions or alternatives. The context of 'from CoinGecko' is clearly stated.

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