get_token_price

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

With no annotations, the description carries the full burden, but it only mentions 'via metadata', giving a hint about data source without disclosing caveats like price freshness, potential null results, or whether the data is live. It does not clarify if this is a read-only operation or if failures are possible.

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, clear sentence with no unnecessary words. It front-loads the core action and source, making it easy to scan and understand.

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 simple one-parameter read tool, the description is minimally sufficient but lacks important context such as return value format, error behavior, or data reliability. No output schema exists, so the description could provide more guidance, but the tool's simplicity keeps this at a mid-range score.

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 has one parameter 'address' with no description, and the schema coverage is 0%. The description only says 'token' which implies that 'address' is the token's address, but it doesn't specify the address type (e.g., mint, SPL) or any format requirements. Minimal value is added beyond the parameter name.

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 function with a specific verb ('Get') and resource ('current price of a token'), and the source ('from Solscan') differentiates it from sibling tools like get_token_meta. It is distinct and unambiguous.

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 implies the tool is for retrieving token prices, but it provides no explicit guidance on when to use it over alternatives or any exclusions. Sibling tools exist for other token-related data, but no comparison is made.

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