place_order

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

With no annotations, the description discloses key behaviors: the approval mechanism for large notional orders, idempotency support via idempotency_key, and auto-execution default. However, it does not explain what the 'deviation' parameter does or mention error handling.

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 with three sentences. The first sentence front-loads the core purpose. While it could be more structured (e.g., bullet points), it avoids unneeded detail and is 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 complexity (13 parameters, no output schema, no annotations), the description covers main behavior and the approval flow but omits details like return values, validation rules, and the meaning of 'deviation'. It is adequate but not comprehensive.

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 0%, so the description must compensate. It mentions SL, TP, deviation, approval_confirmed, and idempotency_key, but fails to describe symbol, side, type, volume, price, stop_limit_price, and comment. Only partial parameter meaning is provided.

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 market or pending order' with specific verb and resource. It distinguishes from siblings like cancel_order, modify_order, get_orders by focusing on order creation. The mention of optional SL/TP/deviation adds specificity.

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 implies use for new orders but does not explicitly state when to use this tool vs alternatives (e.g., modify_order for existing orders). No when-not-to-use guidance is provided, though the context is clear.

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