What the documents look like
Livestream after-sales work arrives in bursts after a single high-traffic session. Refund applications, reshipment orders and script templates come in during the same window, and whether the host's on-air promises match the order list decides whether customer service can give one consistent explanation. The materials for this category are the livestream order list, refund applications, reshipment orders and script templates, drawn from shop after-sales records, customer-service IM, warehouse WMS and logistics tracking. The comparison task on this page places the subject, product, amount, status and validity scope of these materials onto the same fields and checks them item by item.
Tool calls and plugins let the model decide, from a tool description and parameter descriptions, whether to invoke a system module or plugin to complete one comparison pass. The tool description states the purpose and the calling conditions; the parameter description and the required flag together affect the call outcome. By default the tool call node returns the tool result to the AI for summarization. When a tool call termination node is attached, the current call ends, no further tools are called, and the AI no longer answers from the tool result.
Constraints at the tool calls step
A tool call does not replace authorization. A retrieved refund application shows only that the record was recalled within the retrieval scope. It does not show that the refund was approved, and it does not show that a reshipment was executed. When a required parameter has no suitable value in context, the model may not call the tool; the prompt then guides the user to supply the parameter, and the actual request content is checked. System module parameters are fixed, plugin parameters are configurable, and both are checked against the real fields. A parameter description is not a guarantee of execution.
In advanced orchestration, connecting an available tool to the tool call module allows its description to be edited so the call timing is narrower. The official guidance is to start with a small number of tools, tune them, then add more. A tool call termination node placed after a tool forces the current call to end. Custom variables extend tool input so that nodes not treated as tool parameters can also be called. These are existing node behaviors or configurable fields. Business approval, database writes and external synchronization still require a separate system implementation.
Configuration and implementation checks
Hypothetical drill sample: the source material reads "Order A-01, product shampoo 500ml two units, buyer submitted a refund application on March 2, reason one unit short." The warehouse reshipment order B-07 states "March 3, reship shampoo 500ml one unit, status pending review." The draft sentence to be judged is "The shortage on this order has been fully handled and the reshipment has been sent." The configuration below centers on this sample.
| Configuration item | Setting on this page | How to check |
|---|---|---|
| Tool description | States that the comparison covers order list, refund application, reshipment order, script template | Check whether the description includes input conditions and cases where the tool should not be called |
| Tool parameters | Plugin parameters set to real fields; system module parameters fixed | Check parameter description and required flag; do not treat the description as an execution guarantee |
| Required parameters | When no suitable required parameter exists, the model may not call the tool | Guide the user through the prompt to supply it, then check the actual request |
| Tool connection | In advanced orchestration, connect available tools to the tool call module | Tune a small number of tools first, then add more |
| Tool call termination | Placed after a tool to end the current call | Confirm no further tools are called and no AI summary follows |
| Custom variables | Add variable descriptions for nodes not treated as tool parameters | Check the variable description against the corresponding node |
Hypothetical trial starting point: restrict the tool description to "call only when the order list, refund application and reshipment order all appear together and their fields can be compared." This starting point is chosen because all three materials are present in the sample, which allows field-by-field comparison. The comparison object is the call scope without the restricted description, observed for calls that occur when material is missing.
Three common errors
- Treating a retrieval hit as completed authorization. The input is the refund application and reshipment order in the sample; the compared field is the reshipment order status "pending review." If the draft sentence reads "fully handled," it does not match the material status. Pending review does not show that reshipment is complete.
- Treating a parameter description as an execution guarantee. The input is the plugin parameter description; the comparison is whether the actual request carries the required parameter. If the request lacks a required parameter while the text describes the action as executed, the text exceeds what the material supports.
- Treating tool call termination as business termination. The input is a termination node attached after the reshipment order lookup; its effect is to end the current call and stop the AI summary. Reading that as "the reshipment has been sent" confuses node behavior with a business action.
How to verify the setup
- Input the three source sentences and the draft sentence from the sample. Compare "fully handled" and "the reshipment has been sent" in the draft against the reshipment order status "pending review" and the refund application status. The condition is met when the draft keeps the "pending review" wording and notes that the reshipment order does not show it has been sent. A status-field mismatch is the observable failure.
- Input the refund application and reshipment order from the sample. Compare subject, product, quantity and date fields, observing whether Order A-01, shampoo 500ml, one unit, March 2 and March 3 correspond item by item. A field that is not stated is recorded as unsupported or pending verification, not as a contradiction.
- Input a paper request containing only the order list, with the refund application and reshipment order absent. Compare against the restricted tool description and observe whether the comparison tool is called. Not calling the tool and indicating missing material meets the restricted description. Calling it and outputting a "fully handled" conclusion is recorded as beyond the material scope.