cap_trade_execute_working_order

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

The description discloses that the tool creates a real order (destructive) and that the SDK enforces safety gates. However, it lacks details on response behavior, error conditions, or required auth, which is significant given no annotations.

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 sentences, each adding value. No fluff.

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?

The tool has four parameters and an output schema, but the description omits the preview-execute flow, parameter semantics, and output details, making it incomplete for an agent.

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 description coverage, the description should explain parameters but only mentions 'previewed working order' without clarifying preview_id, confirm, wait_for_confirm, or timeout_s.

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 the tool executes a previewed working order and creates a real order. It differentiates from sibling tools like cap_trade_preview_working_order and cap_trade_execute_position.

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 implies the tool should be used after previewing a working order, but does not explicitly state when not to use it or list alternatives. The context is clear enough.

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