place_order

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

No annotations exist, so the description carries full burden. It only mentions order types; it does not disclose important behaviors like return values, error handling, permission requirements, or side effects (e.g., immediate submission vs. validation).

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 short and to the point, with no wasted words. However, it could include more critical behavioral details without becoming verbose.

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 (14 parameters, no output schema) and sibling tools, the description is incomplete. It lacks information on return values, prerequisites, and how it interacts with TP/SL parameters or reduce-only. The agent may miss important constraints.

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 100%, so all parameters are already documented. The description adds only the supported order types, which aligns with the orderType parameter. Minimal added value beyond the schema.

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 new futures order and lists supported order types (limit, market, etc.), making the purpose obvious. However, it does not differentiate from siblings like place_algo_order or place_tpsl, which also place 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 is provided on when to use this tool versus alternative order-placing siblings (e.g., place_algo_order, place_tpsl, batch_orders). The agent must infer from the order types mentioned, but no explicit 'do not use' or context is given.

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