sell_stock_stop_loss

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

No annotations provided, and the description fails to disclose important behavioral traits such as how the stop loss triggers (e.g., becomes a market order), order duration, or potential partial fills. Minimal transparency beyond the basic action.

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 concise, using a brief sentence plus an Args list. However, the list takes up unnecessary space and could be less verbose. Still, it is front-loaded with the purpose.

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?

Even with an output schema, the description omits critical context for a stop loss order, such as order validity, trigger behavior, or price conditions. It does not explain how stop_price relates to current market price or other order lifecycle details.

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%, but the description adds only minimal explanations for each parameter (e.g., 'The stock symbol to sell'). It does not provide value ranges, constraints, or examples beyond a single ticker, failing to compensate for the lack of schema descriptions.

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 it places a stop loss sell order for a stock, using specific verb and resource. It distinguishes from sibling sell tools like sell_stock_limit and sell_stock_market.

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?

No guidance on when to use this tool versus alternatives like limit or market sell orders. The description does not mention prerequisites or scenarios where stop loss is appropriate.

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