magicblock swapQuote

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

The description claims it is a lightweight read tier, implying no side effects, but annotations set destructiveHint=true, indicating potential destructive effects. This is a direct contradiction that misleads the agent about behavioral traits.

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 two sentences, direct and front-loaded with the tool's purpose and usage. No redundant information.

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?

The tool has an output schema (not shown but present), so return values are covered. The description provides context about being a proxy for an underlying API and its relation to magicblock_swap. Minor deduction due to the annotation contradiction affecting overall trust, but the description itself is complete for a read-tier tool.

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 schema already documents all parameters. The description does not add meaningful new information beyond the schema, so baseline score of 3 applies.

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 a swap quote between two SPL mints and explicitly mentions it is a proxy for the Triton Metis swap API. It also directs to pass the result into magicblock_swap, distinguishing its purpose from that sibling tool.

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 explicitly says use this before any value-moving swap and pass the result into magicblock_swap. It also calls itself a lightweight read tier, indicating when to use it. This clearly guides the agent on when to invoke this tool versus alternatives like magicblock_swap.

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