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

Annotations only carry destructiveHint=true, so the description does the heavy lifting: it discloses that nothing is charged or produced, that confirmation happens out-of-band in the dashboard, and that the API call must never include 'confirm'. This meaningfully clarifies the write-like nature of the call beyond the lone annotation, though it does not cover auth/rate-limit behavior or the response shape.

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 tight — the draft/no-charge semantics are front-loaded, followed by the confirmation requirement and the per-item identifier rule. Every clause carries information, though the final 'POST /orders (never with confirm)' fragment is dense and slightly telegraphic.

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 an 8-parameter, nested-object mutation tool with no output schema, the description covers the critical unknowns: non-charging draft behavior, later confirmation, and the item identifier options. It leaves the return payload and auth/store-token nuance to the schema, which is acceptable given the 100% schema coverage.

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 the baseline is 3, but the description adds real value by stating the mutually-exclusive item identifier requirement (one of variant_id + files, sync_variant_id, external_variant_id, warehouse_product_variant_id, or product_template_id + variant_id) — a constraint the schema does not express on its own.

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 a specific verb+resource ('Create an order as a DRAFT') and immediately scopes the behavior ('nothing is charged or produced'), which cleanly separates it from siblings like printful_update_draft_order, printful_list_orders, and printful_get_order. An agent can identify the tool without opening the schema.

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?

Explains the post-creation lifecycle (must be confirmed later in the Printful dashboard, where the charge is shown) and the endpoint rule ('POST /orders, never with confirm'). It does not explicitly route the agent against alternatives such as printful_estimate_order_costs or printful_calculate_shipping_rates, so it stops short of full when/when-not guidance.

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