preview_market_order

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

With no annotations, the description carries the full burden and does well: it explicitly states the tool does not place an order, describes the five-minute preview nature, and specifies the required confirmation workflow. These are meaningful behavioral traits beyond what the schema conveys.

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?

Two sentences, no filler. The core purpose and the critical safety constraint ('does not place an order' and 'wait for user to directly confirm') are front-loaded and concise.

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 schema fully documents parameters and the description covers purpose, non-execution, and the confirmation workflow, the agent has everything needed to invoke the tool correctly and route the result to execute_confirmed_action. No output schema exists, but the instruction to 'Present every detail' covers handling the result.

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 the schema already documents ticker, quantity, and extendedHours thoroughly. The description adds only the context that the order is a buy or sell market order, which aligns with the quantity sign semantics but doesn't materially expand on 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 uses a specific verb ('Create') and resource ('preview for a real buy or sell Market order'), and immediately distinguishes itself from execution by stating 'It does not place an order.' This clearly differentiates it from siblings like execute_confirmed_action and preview_order_cancellation.

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 clearly states when to use this tool: before placing a real market order, and instructs the agent to wait for direct user confirmation before calling execute_confirmed_action. It doesn't explicitly discuss alternatives like limit orders or cancellation previews, but the main execution-vs-preview distinction is well covered.

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