Jupiter Get Price

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds that prices are 'heuristic' and supports extra info, but does not disclose potential issues like data staleness or rate limits. It adds modest value beyond annotations.

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 concise with two sentences: one for purpose and one for SAP MCP context. The second sentence is useful but somewhat generic for Jupiter tools. Efficient but could be slightly more tailored to this specific tool.

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 existence of an output schema (so no need to describe return values), the description covers purpose and key features. It adequately informs the agent about the heuristic nature and optional extra info, though it could mention that prices are approximate.

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 description coverage is 100%, with each parameter having clear descriptions (e.g., vsToken: 'Token mint address (base58)'). The description adds 'Supports buy/sell price, confidence, and depth info,' which aligns with the showExtraInfo parameter but does not provide new meaning 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?

The description clearly states the tool fetches real-time heuristic prices for tokens, specifying support for buy/sell price, confidence, and depth info. While it distinguishes from other Jupiter trading tools, it lacks explicit differentiation from similar price tools like coingecko_getTokenPrice or pyth_getPrice.

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 mentions SAP MCP context and that Jupiter tools are for quote/route/swap preparation, but does not provide specific guidance on when to use this tool versus alternatives. No when-not-to-use or exclusion criteria are given.

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