place_stock_order

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

With no annotations, the description carries the full burden. It clearly discloses that this sends a real order to Firstrade, that it requires a confirm_token, and that the server enforces the preview requirement. It could add more about side effects (e.g., irreversible, funds affected), but the core behavioral traits are well covered.

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 well-structured with a clear opening warning, then a compact parameter list. It is slightly long but every line earns its place by adding necessary usage detail. The front-loaded warning about live orders is appropriately placed.

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 tool's complexity (8 params, live order side effects, no annotations), the description covers prerequisites, parameter semantics, and the preview-token requirement. It mentions returns JSON with order confirmation, and an output schema exists. Minor gaps: no explicit statement about reversibility or error cases, but the description is largely complete for safe invocation.

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 does: it explains each parameter's meaning, provides examples for symbol, enumerates valid values for order_type, price_type, and duration, and clarifies conditional requirements for price and stop_price. This is strong compensation, though it doesn't detail the exact return JSON structure.

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 states a specific verb ('Place'), a specific resource ('real stock order'), and immediately distinguishes itself from preview_stock_order by noting dry_run=False. It also names the sibling preview_stock_order explicitly, making the tool's role clear.

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 explicitly states the prerequisite (FT_ALLOW_LIVE_ORDERS=true) and the mandatory precondition (confirm_token from preview_stock_order with exact same arguments). It also explains the server rejects otherwise, which tells the agent when this tool is appropriate and what must happen before calling it.

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