wsCreateOrder

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

With no annotations, the description carries full burden. It clearly states the tool places/modifies real orders, that the response is just an acknowledgment, and directs users to verify order status via other means. No contradictions.

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 two short paragraphs. The first states the core purpose, the second adds critical usage guidance. Every sentence is meaningful and front-loaded.

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 30 parameters and no output schema, the description adequately explains the acknowledgment nature and where to verify orders. It lacks details on error handling or return format, but covers essential context.

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 coverage is 100%, so baseline is 3. The description adds no additional meaning beyond the schema, except the note to confirm certain parameters. The parameter descriptions in schema are adequate.

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 it places new orders via WebSocket, using a specific verb and resource. It distinguishes from REST equivalents (createOrder) but does not explicitly differentiate from other WebSocket order tools like wsAmendOrder.

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 IMPORTANT note tells users to confirm symbol, side, quantity, and price before calling, and explains that the response is only an acknowledgment, advising to use subscribeOrder or REST endpoints for verification. It does not provide when-not-to-use or alternatives for amendments.

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