Place Stop Order

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

Beyond annotations, the description discloses key behavioral traits: non-idempotency (NOT idempotent), rate limit (1 req / 2s), trigger based on Last Traded Price, and side semantics for quantity. It adds significant contextual value that annotations alone do not convey.

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 four sentences, each carrying essential information: order type, trigger source, side handling, idempotency, and rate limit. It is front-loaded with the core purpose and avoids any unnecessary words or repetition.

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?

With no output schema, the description does not explain return values, which is a minor gap. However, it thoroughly covers the order logic, side semantics, rate limit, and idempotency, and the schema fully documents all parameters, so the tool can be correctly invoked with confidence.

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 baseline is 3. The description adds extra meaning by clarifying that stopPrice is triggered by Last Traded Price (beyond schema's 'Price that triggers the market order') and reinforces the buy/sell quantity convention. This added specificity justifies a 4.

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 action: "Place a STOP order that triggers a market order once the stop price is reached." It specifies the verb (Place), the resource (STOP order), and the unique behavior (triggered by Last Traded Price), distinguishing it from sibling order tools like market or limit.

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 usage context: positive quantity for buying, negative for selling (stop-loss), and the trigger mechanism. However, it does not explicitly name alternatives or state when *not* to use this tool versus place_stop_limit_order, leaving some exclusions implicit.

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