place_short_order

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

The description warns 'This executes a real trade.' beyond annotations (destructiveHint=false). However, it does not detail risks like margin requirements or potential losses.

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: a brief intro, a warning, and a bulleted parameter list. Every element adds value without redundancy.

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?

Covers the essential: action, parameters, and warning. Given an output schema exists, return values need not be explained. Could add more context about market conditions for shorting.

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?

With 0% schema coverage, the description provides exhaustive parameter explanations (symbol, quantity, order_type, etc.), adding significant meaning beyond the schema's bare names.

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 'Place an equity short-sale order.' and distinguishes from siblings like preflight_short_order and place_order (which may be for long orders). The warning about real trade adds clarity.

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 explicitly recommends running preflight_short_order first, providing a clear alternative. It does not explicitly state when not to use, but the warning implies caution.

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