solana_get_price

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

With no annotations provided, the description must disclose behavioral information. It only states the API gets a price, omitting details like authentication requirements, rate limits, error handling, or whether it's a cached or live price. For a simple read operation, more transparency is needed.

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?

A single sentence that conveys the tool's core purpose without any wasted words. It is front-loaded and efficiently structured.

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 simplicity (no parameters, no output schema), the description is largely complete. However, the lack of behavioral transparency (e.g., what authentication is needed, if any) slightly reduces completeness. Still, for a basic price query, it is adequate.

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 has zero parameters (coverage 100%), so the description does not need to add parameter details. Per guidelines, baseline is 4. The description does not attempt to describe non-existent parameters, which 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 gets the current SOL price in USD. It uses a specific verb 'get' and resource 'SOL price in USD', effectively distinguishing it from siblings like solana_get_balance (balance) and solana_get_token_info (token info).

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 explicit guidance on when to use this tool vs alternatives. However, the purpose is straightforward and the sibling tools cover different functions (balance, token info, transaction), so the intended use case is implied. A brief note on when to prefer this over others would improve usability.

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