place_order

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

No annotations are provided, and the description fails to disclose important behavioral traits such as execution timing, order cancellability, partial fills, or required permissions. For a trading order tool, this is a significant gap.

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 concise and front-loaded with examples, making it quickly scannable. However, it could be structured more clearly (e.g., list parameter descriptions) without losing brevity.

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 complexity (10 parameters, 5 required) and lack of output schema or annotations, the description covers the core order types but omits exchange and tif parameters. It also doesn't explain return values or confirmation flow, leaving gaps for a trading 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?

The description uses examples to explain many parameters (accountId, symbol, action, orderType, quantity, price, stopPrice, suppressConfirmations), but schema coverage is 0% and parameters like 'exchange' and 'tif' are not mentioned. It provides partial but not complete semantic guidance.

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 'Place a trading order.' This is a specific verb+resource combination that distinguishes it from sibling tools like confirm_order, get_order_status, or get_live_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?

The description provides multiple examples covering market, limit, stop orders, and suppress confirmations, which implicitly guide when to use these variations. However, it lacks explicit 'when not to use' or direct comparison to alternative tools like confirm_order.

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