preCheckOrder

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

With no annotations, the description carries full burden. It discloses the tool does not place orders, returns pre/post margin rates in E4 format, and only works for linear and option categories. It does not mention authentication, rate limits, or detailed response structure, but covers key behavioral aspects adequately.

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 somewhat repetitive with an Agent hint and TradFi note that restate the same core information. It could be streamlined into a single concise paragraph without losing clarity.

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 21 parameters, no output schema, and no annotations, the description is insufficient. It fails to explain the response format in detail, provide parameter guidance, or cover prerequisites. The tool is moderately complex but the description only addresses basic purpose.

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 0% with 21 parameters. The description only states 'Request parameters are the same as Create Order' without explaining any parameter meaning, format, or constraints beyond what enums provide. This fails to add value for the agent.

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 validates an order before placing it to check margin requirements. It specifies it is for futures and options only (linear, option categories) and distinguishes itself from createOrder by noting it does not actually place the order.

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 explicitly says to use this endpoint to validate margin requirements before placing an order, and that it does not create orders. It states only works for futures and options, implying not for other categories, but could be more explicit about when not to use.

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