jupiter_getQuote

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

Discloses non-destructive read-only nature (quote retrieval) and the Metis engine, providing sufficient transparency given no annotations. Could be improved by explicitly stating it does not execute a swap.

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?

Single sentence with no fluff, effectively communicating core function and distinguishing feature. Perfect conciseness.

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 clear purpose, description lacks details on return values (no output schema) and default behaviors for optional parameters. Incomplete for a complex tool with 11 parameters.

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 coverage is 73%, so description adds no parameter-level detail beyond schema. Baseline 3 is appropriate; no additional value from description.

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?

Description clearly states 'Get an optimally-routed swap quote with full route plan details (Metis engine)', specifying the verb, resource, and unique features (Metis engine, optimal routing) that distinguish it from sibling tools like jupiter_getPrice or jupiter_swap.

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?

Implied usage for obtaining a quote before swapping, but lacks explicit guidance on when to use versus alternatives (e.g., jupiter_getPrice) or when not to use. No prerequisites or context provided.

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