send_order

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

No annotations provided, so description carries full burden. Discloses validation and auto-routing but omits important traits: is it destructive? What happens on failure? Are there rate limits? Response format? Insufficient for a mutation tool with 7 params.

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?

Two concise sentences front-loaded with core action. Efficient with zero wasted words.

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?

Complex tool with 7 params, no annotations, no output schema. Description fails to cover return values, error handling, prerequisites (e.g., FIX session), or order lifecycle. Incomplete for reliable agent usage.

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%, so description must compensate. Only explains symbol validation and venue auto-route. Other parameters (side, quantity, order_type, price, client_name) lack any explanation beyond schema, which is minimal.

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?

Description clearly states action ('Send a new order'), method ('via FIX NewOrderSingle'), and key behaviors (validates symbol, checks corp actions, auto-routes). It distinguishes from sibling tools like 'send_algo_order' by specifying the order type.

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 explicit guidance on when to use this tool vs alternatives. Mentions auto-routing behavior but lacks exclusion criteria or prerequisites (e.g., FIX session must be active). Sibling tools like 'send_algo_order' exist but no differentiation.

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