Place Market Order

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

Beyond annotations, the description adds a slippage warning, emphasizes non-idempotency ('duplicate calls create duplicate orders'), and discloses the rate limit. These behavioral traits are useful for an agent. No contradiction with annotations.

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?

Three sentences, front-loaded with the core purpose, and each sentence earns its place (execution type, quantity convention, warnings, rate limit). No redundancy or fluff.

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 and lack of output schema, the description covers execution semantics, side effects (duplicate orders), and rate limits. It does not mention return format or error scenarios, but this is not critical given the schema and sibling context.

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 input schema already has 100% coverage, including descriptions for ticker, quantity, and extendedHours. The description repeats the positive/negative quantity rule already present in the schema, adding little new semantic value.

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 specifies a clear verb ('Place') and resource ('MARKET order'), and the phrase 'immediate execution at the next available price' differentiates it from sibling tools like place_limit_order, place_stop_order, and place_stop_limit_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 gives context for use via 'immediate execution' and warns about price slippage, but it does not explicitly state when to prefer this over limit/stop orders or list any alternatives. The quantity sign rule and rate limit also provide guidance.

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