preview_order

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

With no annotations, the description effectively discloses that the tool is non-destructive (nothing reaches matching engine) and requires API credentials. It also describes the outputs (margin, equity, fee impact), which is transparent for a preview tool.

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 with no waste. The key purpose is front-loaded: 'Preview an order without submitting it'.

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 no output schema, the description adequately explains what the tool returns (margin, equity, fee impact) and mentions credential requirements. It lacks error conditions or limitations but is sufficient for a simple preview.

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 coverage is 100%, so baseline is 3. The description adds that it takes the same arguments as `place_order`, but otherwise does not enrich parameter meaning beyond the schema descriptions.

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 tool previews an order without submitting, projects margin/equity/fee impact, and distinguishes itself from `place_order` by noting it takes the same arguments but nothing reaches the matching engine.

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 implies when to use (to preview order impacts before submission) and mentions it requires API credentials, but does not explicitly state when not to use or compare to other tools like `amend_order` or `cancel_order`.

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