place_twap_order

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

With no annotations, the description only discloses the basic order splitting behavior. It does not mention side effects like order creation, destruction, authorization needs, or rate limits—important for a trading action.

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 very concise with two sentences, front-loading the key purpose. However, the second sentence could be integrated more 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?

Given the tool's complexity (8 parameters, no output schema, multiple sibling variants), the description omits critical context such as prerequisites, error handling, order lifetime, and differentiation from similar TWAP orders.

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 50%, placing the burden on the description to add meaning. The description only restates the action enum values already in the schema, adding no new insight for other parameters like wallet_address, token_address, or slippage.

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 places a TWAP buy or sell order and explains the slicing mechanism. However, it does not distinguish this TWAP order from sibling tools like place_limit_twap_order or place_trailing_twap_order.

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 provides no guidance on when to use this tool versus alternatives such as limit or trailing TWAP orders. There is no explicit context about prerequisites or scenarios where this tool is appropriate.

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