execute_swap_transaction

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

With no annotations provided, the description carries the full burden and excels: it warns about irreversible spending, mentions signing with a configured private key, and outlines the execution steps. It also discloses the non-reversible nature and actual cost, going well beyond basic read/write hints.

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?

Although long, the description is efficiently structured with a clear warning, numbered steps, args, returns, and an example. Every section adds critical information and none is redundant or filler, making it appropriate for a high-stakes operation.

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?

For a complex, irreversible transaction tool, the description covers the execution pipeline, prerequisites (quote retrieval), parameter meanings, return format, and an example. It is fully self-contained even without an output schema shown, addressing all necessary context.

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 schema provides only type and title, but the description explains 'transaction' is a base64 encoded UNSIGNED transaction from get_swap_quote and 'request_id' is from the swap quote response. This contextualizes both parameters and even includes an example showing exactly how to pass them, compensating fully for zero schema coverage.

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 it 'Sign and execute a swap transaction via Jupiter Ultra API' and emphasizes it executes a REAL trade spending actual SOL. This distinguishes it from sibling tools like execute_limit_order while specifying the exact resource (swap transaction) and action (execute).

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?

It explicitly says 'Only call this function when you want to actually execute a trade' and provides a clear pre-requisite flow via get_swap_quote. The example shows the sequence of obtaining a quote then executing, making when-to-use unmistakable.

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