create_order

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

No annotations provided, and the description does not disclose behavioral traits beyond 'create'. It does not mention side effects (e.g., funds movement, order persistence), required permissions, or whether the operation is destructive. The mention of request/response containers is minimal context.

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?

Very short (two sentences), front-loaded with the verb and resource. Minor grammar issue ('a order'), but otherwise 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?

Given the complexity of order creation (multiple order types, many required fields with interdependent logic like target_value vs delta_percentage), the description is too minimal. It fails to explain the semantics of the three order types or the relationship between parameters. Output schema is mentioned but not detailed.

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?

The description does not add parameter information; it relies on the input schema which has detailed descriptions for subfields. However, the top-level parameter lacks a description, and the description provides no extra guidance. Schema already covers subfields well, so baseline 3.

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?

Clearly states the action ('Create a order') and specifies three types (limit, take profit, stop loss). It distinguishes from sibling tools like 'cancel_order' or 'create_dca_order' by naming the order types, though it could be more precise about the resource (token 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?

No guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. Only lists order types without context on when each type is appropriate.

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