get_sol_price

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

The description adds the context 'via Jupiter', disclosing the data source. However, no annotations are provided, and the description does not mention side effects, rate limits, or whether the price is real-time. It is adequate for a simple read operation.

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 sentence of 9 words, front-loaded with the verb and resource. It contains no extraneous information and is highly efficient.

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 zero parameters, no output schema, and a straightforward purpose, the description fully covers the necessary context. The source (Jupiter) is disclosed, and the sibling tools provide enough differentiation.

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 no parameters, and schema description coverage is 100%. According to the rules, baseline is 3 when coverage is high. The description adds no parameter info, which is fine as there are none.

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 action (Get), the resource (current SOL price in USD), and the source (via Jupiter). It distinguishes itself from siblings like get_token_price (for other tokens) and get_swap_quote (for swap quotes).

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 when to use it (when needing SOL price) but does not explicitly mention when not to use it or provide alternatives. The sibling list includes other price tools, but no guidance on selection.

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