solana_execute_swap

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

With no annotations, the description must disclose behavioral traits itself. It does mention that the private key comes from the environment, which is useful, but it omits critical facts: this is a state-changing transaction that incurs gas fees, may fail due to slippage/price movement, and is irreversible. The description does not explicitly warn about potential loss of funds.

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 one concise, front-loaded sentence with no unnecessary words. It communicates the essential action and context efficiently.

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?

This is a complex state-changing operation with no output schema and no annotations. The description fails to mention the return format (e.g., transaction signature), possible failure modes, or prerequisites like obtaining a quote. The single sentence leaves significant gaps for an agent attempting to use the tool correctly.

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?

All four parameters have schema descriptions, so baseline is 3. The tool description adds no additional parameter semantics beyond what the schema already provides, such as format or constraint details. The note about the private key being from the environment implicitly explains why no private key parameter exists, a minor addition.

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 executes a token swap using the Jupiter DEX aggregator on Solana. The verb 'Execute' and resource 'token swap' are specific, and the mention of Jupiter and environment private key distinguishes it from other Solana tools like solana_get_swap_quote and generic execute_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?

The description gives no guidance on when to use this tool versus alternatives, such as first fetching a quote via solana_get_swap_quote, nor does it mention prerequisites like token approval or sufficient balance. It provides no exclusions or conditions for use.

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