auto_swap

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

Discloses that it performs multiple operations in one step and requires a private key, but lacks details on side effects, error handling, or additional requirements. No annotations 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 pithy sentences, immediately informative without extraneous content.

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?

Despite 6 parameters and no output schema, the description omits explanation of parameters and return value, severely limiting practical use.

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?

With 0% schema description coverage, the description adds no information about the 6 parameters, failing to explain fields like holdings_percentage, slippage, or amount.

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 clearly states the tool combines build, sign, and submit in one step, differentiating it from siblings like build_swap and submit_signed_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?

Only mentions the requirement of TRADEROUTER_PRIVATE_KEY but provides no guidance on when to use this tool versus alternatives like build_swap or submit_signed_swap.

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