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

Annotations (readOnlyHint=true, idempotentHint=true, destructiveHint=false) already declare safety. The description adds key behavioral traits: it returns an unsigned transaction, never receives keypair bytes, and value-moving results must be finalized locally. This fully discloses behavior beyond annotations without contradiction.

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 includes lengthy SAP MCP context and execution guidance that, while useful, makes it longer than necessary. The core purpose is stated upfront, but the second paragraph is dense and could be more concise. A shorter version would be more 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 the tool's complexity (7 params, no nested objects, output schema) and rich annotations, the description covers purpose, behavior, and usage guidelines adequately. The only minor gap is explicit differentiation from jupiter_getQuote, but the description implies it through 'Ultra API' and 'recommended entry-point'. Overall, it is sufficiently complete.

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%, so the baseline is 3. The description does not add extra parameter-specific details beyond the schema, but the schema's field descriptions are informative. No additional enrichment is provided.

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 purpose: 'Get a quote + unsigned swap transaction in a single call (Ultra API). The recommended entry-point for swaps.' It uses a specific verb ('Get') and resource ('quote + unsigned swap transaction'), and distinguishes itself from sibling tools like jupiter_getQuote and jupiter_swap by being a combined call.

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 provides explicit guidance: it is 'the recommended entry-point for swaps' and advises using SAP transaction preview/sign/submit tools afterward for signing. It also mentions pricing and routing steps (e.g., call sap_estimate_tool_cost first), offering clear when-to-use and when-not-to-use instructions.

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