Place Order

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

Annotations already mark destructiveHint=true. The description adds value by revealing that orders default to SIM and that LIVE requires environment variables and policy, including potential caps. This goes beyond annotations, though more details about side effects (e.g., risk checks) could be added.

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?

Three sentences: first states purpose, second and third provide critical constraints. No unnecessary words; front-loaded and efficient.

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?

Despite complex schema (13 params, nested objects, required fields), the description lacks explanation of multi-leg ordering (though that's a sibling), order duration structure, or output expectations. The agent would need more context to use this tool correctly.

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 the description should compensate. It only mentions policy caps on Amount/AssetType/AccountKey/Uic/notional, which gives high-level constraints but does not explain each parameter's meaning or usage. For 13 parameters, this is insufficient.

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 states 'Place a new Saxo order' which is a specific verb + resource. It distinguishes from siblings like cancel/modify/multileg orders by focusing on single order placement. Adding the default SIM vs LIVE context further clarifies scope.

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 mentions default SIM and LIVE requirements, providing some context. However, it does not explicitly guide when to use this tool vs siblings like saxo_place_multileg_order or saxo_precheck_order, leaving the agent to infer from names.

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