Precheck Multi-Leg Option Order

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

The description claims validation without placing, but annotations indicate destructiveHint=true and readOnlyHint=false, implying state modification. This contradicts the description, creating significant confusion about the tool's behavior.

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 concise (3-4 sentences) and front-loads the core purpose. Every sentence adds value, with no unnecessary words.

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 the tool's complexity (multi-leg options, 7 params), the description covers key constraints but omits explanation of OrderDuration enums and the meaning of ManualOrder/ExternalReference. The annotation contradiction also undermines completeness.

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?

With 0% schema description coverage, the description adds essential meaning: OrderPrice is always positive and absolute, OrderType must be Limit, and legs require same option root. It compensates well for the schema 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 clearly states the tool validates multi-leg option strategies without placing them, and lists specific strategy examples (vertical, calendar, condor, straddle), distinguishing it from other order 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?

It explicitly states OrderType must be Limit, OrderPrice must be positive, explains debit vs credit inference, and mandates that all legs share the same option root, guiding correct usage.

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