preview_order

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

No annotations provided, so description fully covers behavior: it does not send the order, returns a one-time confirmation token under conditions, and provides risk decision.

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 plus a parameter note, highly front-loaded with essential purpose and flow. No redundant or extra sentences.

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?

Explains the tool's role in a two-step process, what it returns, and key conditions. Minor gap: no mention of error handling or what happens if trading is disabled.

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?

Adds meaning for action (BUY/SELL) and order_type (MKT/LMT with limit_price required for LMT). Symbol and quantity are not further explained. With 0% schema coverage, partial compensation.

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 it is 'STEP 1 of 2 for trading' and validates a proposed order without sending it. It distinguishes from place_order and specifies the return values.

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 to call place_order after with the token, and notes requirements for order types. Lacks explicit 'when not to use' but sibling tools and context provide clarity.

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