Place Limit Order

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

The description goes beyond annotations by explicitly warning about non-idempotency (duplicate orders) and disclosing the rate limit. It also explains execution price semantics, which are not included in annotations. This adds significant behavioral context beyond the structured fields.

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 three sentences with a front-loaded purpose, followed by critical usage and behavioral notes. No redundant text; every sentence serves a purpose. It is appropriately concise for a tool with this 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?

Given the moderate complexity (4 parameters, no output schema), the description covers purpose, execution behavior, non-idempotency, and rate limiting. It provides enough information for an agent to invoke the tool correctly and handle expectations, with no significant gaps.

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 100%, so the baseline is 3. The description adds value by clarifying how the sign of quantity maps to buy/sell and that execution occurs at limitPrice or better, which reinforces and expands schema descriptions. It does not introduce new parameter details but enhances understanding.

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's function: placing a limit order that executes at a specified price or better. It distinguishes this from sibling order types (market, stop, stop-limit) by the explicit 'LIMIT order' terminology and the price execution logic.

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 provides clear operational guidance: sign of quantity determines buy vs. sell, and execution price bounds are specified. It does not explicitly name alternative tools for comparison, but the behavior is detailed enough for an agent to select this tool when a limit order is needed.

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