preview_order

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

With no annotations provided, the description must carry the behavioral burden. It does disclose that the tool checks multiple limit types, but does not explicitly state whether it is read-only, what happens on violation, or whether any state is affected. 'Dry-run' implies no actual order, but the absence of explicit assurances leaves some ambiguity.

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 sentence, front-loaded with the key action ('Dry-run'), and every word adds value. There is no fluff or redundancy.

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 tool has an output schema and 5 parameters, but no annotations. The description provides a clear high-level purpose but fails to cover usage context, parameter semantics, or what the output represents. Given the existence of an output schema, some return details may be elsewhere, but the overall description is under-specified for a tool with this complexity.

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 0%, yet the description does not mention any parameter names, formats, or acceptable values (e.g., side values). While some parameter names are self-explanatory, the lack of guidance on required fields like account, symbol, side, and qty beyond the schema is a significant gap.

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 the specific verb 'Dry-run' and clearly states the resource ('an order') and the scope ('against cash, margin, short, naked-option, and leverage limits'). This distinguishes it from sibling tools like order_submit, which actually places orders.

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 term 'Dry-run' clearly implies a non-executing preview, providing context for use before placing an actual order. However, it does not explicitly name alternatives or state when not to use, but the implied usage is clear enough for an agent.

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