swap_transaction

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

Description lacks behavioral details such as on-chain execution, irreversibility, permission requirements, or error handling. No annotations exist to compensate.

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?

Two sentences, front-loading the purpose, but the description is too brief to provide necessary context while remaining clear.

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 complex nested schema and no annotations, the description omits prerequisites, output schema details, and error conditions, leaving the agent underinformed.

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?

Description names the expected container type but does not explain the meaning of 'transaction_id' or how to obtain it. Schema has 0% description coverage, and the description adds minimal semantic value.

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 states 'Execute a swap transaction' with input/output types, clearly identifying the action and resource. Distinguished from sibling tools like 'swap_quote' by focusing on execution.

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?

No guidance on when to use this tool vs alternatives (e.g., 'swap_quote' for quoting, 'stake_transaction' for staking) or prerequisites like obtaining a transaction_id from a quote.

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