place_order

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

Warns that 'This executes a real trade', adding critical behavioral context beyond annotations which only set readOnlyHint=false. Details parameter dependencies (e.g., limit_price required for LIMIT orders) and mutual exclusivity of quantity/amount.

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?

Efficiently structured: summary line, warning, then parameter list. No redundancy, and the parameter docstring is necessary given the tool's complexity.

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?

Covers all aspects: purpose, usage guidelines, parameter semantics, and behavioral warnings. With an output schema present, the description does not need to detail return values, making it complete for agent invocation.

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 fully compensates by explaining every parameter, including defaults, constraints, and usage notes (e.g., open_close_indicator for options, equity_market_session for equities).

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 'Place a single-leg order (buy/sell stocks, crypto, or options)', which specifies the verb and resource. It distinguishes from siblings like 'place_multileg_order' by emphasizing 'single-leg'.

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?

Explicitly recommends using 'preflight_order' first, providing clear context for when to validate before executing. Does not explicitly state exclusions for other order types, but the single-leg specification and sibling names imply appropriate usage.

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