place_limit_order

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

No annotations provided. Description mentions 'over WS' implying WebSocket usage but does not disclose behavioral traits like order lifetime, execution guarantees, or required permissions for a mutation operation.

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?

One short sentence, concise but not well-structured. Lacks separation of concerns (e.g., parameters, behavior). Could be reorganized for clarity.

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?

With 8 parameters, no output schema, and no annotations, the description provides minimal context. Missing prerequisites, return values, and usage examples for a complex order placement 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?

Description only explains the 'action' and 'target' parameters. The other six parameters (wallet_address, token_address, amount, holdings_percentage, slippage, expiry_hours) are not described, despite schema coverage being 0%.

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?

Clearly states the tool places a market-cap-based limit order, specifying the action (sell/buy) and target as bps relative to market cap. This distinguishes it from sibling tools like trailing or TWAP orders.

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 versus alternatives (e.g., trailing, TWAP, or simple swaps). The description lacks context for selection among many similar siblings.

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