preflight_short_order

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description reinforces that the tool does not place an order, but adds no further behavioral context (e.g., authorization needs, rate limits). With annotations present, the description's added value on behavior is minimal.

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 with a brief purpose statement followed by a well-organized Args list. Every sentence adds value, and there is no extraneous content. It is front-loaded with the core 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?

Given the tool has an output schema (not shown but provided), the description does not need to explain return values. It covers the tool's purpose, all parameters, and its non-destructive nature. For a tool with 9 parameters, this is complete and sufficient.

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 includes a detailed Args section explaining each parameter's purpose, examples, defaults, and conditions (e.g., 'limit_price: Required for LIMIT and STOP_LIMIT orders'). This adds significant meaning beyond the schema's type-only definitions for all 9 parameters.

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 'Estimate costs for a short-sale equity order before placing it', which is a specific verb+resource. It distinguishes from sibling tools like place_short_order (which places the order) and other preflight tools (for spreads or generic orders).

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 says 'Returns estimated commission, fees, and buying power impact. Does NOT place an order.' This clearly indicates when to use it (before placing a short order) and what it does not do. It does not explicitly mention alternatives or when not to use, but the context is clear.

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