vechainstats_get_token_price

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

With no annotations, the description must supply safety/behavior context; it only lists returned fields and 'current' without disclosing data source, staleness, unknown-token behavior, or expanded flag effects.

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?

One sentence with no filler; every word adds relevant detail (current, USD, 24h change, volume).

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?

Despite simple complexity, no output schema or annotations exist, and the optional expanded parameter is undocumented. The description does not clearly differentiate from get_all_token_prices, making it incomplete for confident invocation.

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 documents token as required with examples, but expanded has no description. The description does not explain expanded, so half the parameters lack semantic guidance beyond the 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 the tool fetches a single token's current USD price, 24h change, and volume. The specific resource 'token price' plus 'current' distinguishes it from bulk/quotes and price history, though it does not explicitly name sibling get_all_token_prices.

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 given about when to choose this over vechainstats_get_all_token_prices or token_info. The phrase 'current' implies real-time retrieval but lacks exclusions or alternatives.

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