jlcpcb_tdp_create_order

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

No annotations are provided, so the description carries full burden. It warns 'CREATE A REAL, PAID... order', signaling financial impact, and mentions the disabled gate and credential requirement. It doesn't detail failure modes or idempotency, but the key behavioral traits are disclosed.

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, each purposeful: purpose, enabling condition, and input guidance. Front-loaded with the action verb. No filler or repetition.

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?

For a single-parameter create-order tool with no output schema, this covers purpose, prerequisites, and param source. It could mention the response shape or error behavior, but the essentials are present. The description is adequate for an agent to invoke 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 coverage is 100% (the only parameter `params` is described), but the description adds workflow meaning: the params 'typically from a prior jlcpcb_tdp_calculate_price quote'. It also lists example keys, reinforcing the schema's nested structure. This goes beyond the schema's generic object description.

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 opens with 'CREATE A REAL, PAID 3D-printing order', which uses a specific verb ('create') and resource ('3D-printing order') while emphasizing the real, paid nature. This clearly distinguishes it from siblings like jlcpcb_tdp_calculate_price (pricing) and jlcpcb_tdp_order_list (listing).

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?

It states to pass a `params` object 'typically from a prior jlcpcb_tdp_calculate_price quote', establishing a clear workflow context. It also notes the tool is 'Disabled unless JLCPCB_ENABLE_ORDERS=true', giving a precondition. It doesn't explicitly name alternative tools or when not to use, but the context is sufficient.

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