preview_stock_order

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

With no annotations provided, the description carries the full burden. It clearly states the order is not sent (dry_run=True), and discloses the token's expiry (10 minutes) and single-use nature. It also specifies required parameters for certain order types, which is critical for correct invocation.

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 front-loads the purpose and mandatory usage instruction, then organizes parameters in a compact Args list with inline allowed values. It avoids redundancy and includes only necessary details about the token flow. 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 7-parameter tool with an output schema, the description covers all required guidance: prerequisites, parameter semantics, conditional fields, and the handoff to place_stock_order. No gaps exist that an agent would need to fill.

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?

Despite 0% schema description coverage, the description meticulously documents each parameter with allowed values (e.g., order_type: buy/sell/sell_short/buy_to_cover; price_type: limit/market/...; duration: day/day_ext/overnight/gt90). It also explains the conditional requirements for price and stop_price based on price_type, adding meaning far beyond the raw 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?

States a specific verb and resource: 'Preview a stock order WITHOUT sending it'. This is distinct from siblings like place_stock_order or preview_option_order. The dry_run=True clarification adds precision. Clear and unambiguous.

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?

Explicitly instructs 'Always call this first' and explains that the returned confirm_token must be passed to place_stock_order to actually send the order. This workflow guidance clearly differentiates when to use this tool versus the placement tool, and its scope (stock orders) is implied.

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