ibkr_place_stock_order

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

No annotations are provided, so the description carries the full burden. It only states 'Place a stock order. Paper account only.' It does not disclose important behavioral traits such as whether the order is immediately submitted, what the response contains, error handling, authentication requirements, or potential side effects. For a mutative tool like placing orders, this is insufficient.

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 very concise: two sentences. The first sentence states the core purpose, and the second adds a critical constraint. It is front-loaded and contains no filler. However, it could be slightly expanded to include parameter hints without losing conciseness.

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 has 8 parameters, no output schema, and no annotations, the description is incomplete. It does not explain how to use the parameters, what the tool returns, or how to interpret results. It lacks context for selecting this tool over siblings and does not cover important aspects like order lifecycle or error conditions.

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%, meaning no parameter descriptions exist in the schema. The tool description provides zero information about the 8 parameters (symbol, action, quantity, etc.). It does not explain the meaning of action (BUY/SELL), order type (MKT/LMT), limit price, or other fields. The description adds no value beyond what the schema already shows.

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?

Description clearly states 'Place a stock order' which is a specific verb and resource. The name 'ibkr_place_stock_order' and description distinguish it from sibling tools like 'ibkr_place_option_order' (for options) and 'ibkr_cancel_order' (for cancellations). However, it does not explicitly differentiate from these siblings in the description text.

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 mentions 'Paper account only', which provides a clear constraint on when to use this tool (paper trading environment). However, it does not provide guidance on when to use this tool versus alternatives like 'ibkr_place_option_order' or 'ibkr_cancel_order'. No explicit when-to-use or when-not-to-use information is given.

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