defillama_get_token_prices

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

With no annotations, the description carries the full burden of behavioral disclosure, but it merely says 'Get current prices of tokens'. It does not mention return format, error behavior, rate limits, or underlying data source, offering no insight into how the tool behaves.

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 extremely brief, essentially restating the tool name. While it is concise, it lacks structure and substantive information, making it under-specified rather than efficiently compact.

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 no annotations and no output schema, the description needed to provide comprehensive context for correct invocation. It fails to explain what the tool returns, how to populate the 'coins' parameter, or any limitations, leaving a critical gap for an agent.

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 defines 'coins' as an array of strings with 0% description coverage, and the description does not explain the expected format (e.g., symbols, addresses, chain-qualified IDs). Thus, the description adds no meaning beyond the bare schema definition.

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 retrieves current token prices, using the verb 'get' and resource 'current prices of tokens'. The word 'current' distinguishes it from the sibling tool 'defillama_get_historical_prices', but it doesn't specify the expected identifier format.

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?

No guidance is provided on when to use this tool versus alternatives, such as whether to prefer it for spot prices over historical data. It lacks any context on prerequisites, exclusions, or typical use cases.

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