place_order

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

Annotations indicate the tool is not read-only or destructive, which aligns with placing an order. The description reveals the return value but does not discuss side effects like reduced buying power, potential order failures, or rate limits. Some behavioral context is missing beyond the annotations.

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 two sentences, front-loaded with the core purpose and return value, followed by a targeted usage hint. No unnecessary words; every sentence earns its place.

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?

For a 9-parameter tool with 6 required fields, the description is insufficient. It does not cover error conditions, valid values for transaction_type/order_type, or how to handle optional fields like price and trigger_price. The output schema exists but is not leveraged in the description. Sibling tools like modify_order are not acknowledged.

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?

With 0% schema description coverage, the description adds minimal parameter information beyond the schema. It only clarifies the 'variety' parameter (regular vs. amo). The other eight parameters (tradingsymbol, exchange, etc.) are left unexplained, requiring the agent to infer from names alone.

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 action ('Place a buy or sell order') and the return value ('Returns order ID on success'). It distinguishes between buy and sell but does not explicitly differentiate from sibling tools like cancel_order or modify_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?

Provides guidance on using the 'variety' parameter ('use variety='regular' for normal orders, 'amo' for after-market orders'). However, it does not specify when not to use this tool, such as for modifying or cancelling orders, nor does it mention prerequisites like authentication or margin requirements.

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