Create an order

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

Annotations only flag high-level traits (readOnly=false, etc.). The description adds critical behavioral detail: all money fields are decimal strings, the response is undocumented and returned verbatim, and order state must be tracked via get_orders_state because get_order does not return it.

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?

Four sentences; each delivers a distinct fact: action+endpoint, order_id/body-share, money-format, response, and state-tracking. No wasted words and critical details are 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?

Despite the tool's complexity (10 params, nested objects, no output schema), the description covers the key non-obvious information needed for correct invocation: money string format, opaque response, how to follow up on state, and the client-supplied order_id. It fully compensates for absent output schema and enriches annotations.

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 covers 100% of parameters with descriptions, so baseline is 3. The description adds minimal new parameter-level meaning beyond what's in the schema; 'All money fields are decimal strings' and 'You supply the order_id' reinforce but don't substantively extend the schema's per-field descriptions.

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?

States the specific verb+resource: 'Creates an order on the Yango Tech platform (POST /b2b/v1/orders/create).' The mention of order_id supply and the shared body shape with updates distinguishes creation from update operations, and sibling tools like cancel_order/get_order.

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?

Provides explicit post-creation guidance: 'track progress with get_orders_state (get_order does NOT return the state)' — a clear when-to-use alternative. It also clarifies the order_id is client-supplied, but it doesn't exhaustively contrast with all sibling tools (e.g., cancel_order or update-like flows).

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