Preview Order

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

The annotation readOnlyHint: true already indicates no side effects, and the description reinforces this with 'without placing it.' The description adds clarity about the scope (single-leg or bracket) but does not disclose any other behavioral details such as validation or simulation behavior, which is acceptable given the annotation.

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 a single, concise sentence with no redundant words. It conveys the core purpose and scope efficiently.

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?

The description covers the basic purpose and differentiates from actual order placement. Since an output schema exists, omitting return value details is acceptable. It lacks guidance on when to use it or what a preview entails, but it is sufficient for a straightforward read-only validation tool.

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?

The description refers to the 'order' parameter indirectly by stating 'single-leg or bracket order,' which adds some context. However, it does not explain the structure or required fields of the order object, and the top-level schema has no description coverage. The nested schema provides details, so the description offers marginal added meaning beyond the parameter name.

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 action: preview an order without placing it. It also specifies the scope (single-leg or bracket) and explicitly contrasts with placing, which helps distinguish it from place_order and related tools.

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 usage for validation or pre-submission review, but it does not explicitly say when to use this tool versus alternatives. No mention of alternatives or scenarios where preview should be preferred over place_order or assess_order_impact.

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