What the documents look like
After-sales repair and reship work aims to restore a product to usable condition. Case closure differs from refund-only disputes, because the goal is not a direct refund. The main materials are repair applications, reship orders, inspection reports and accessory outbound orders. These come from the after-sales system, the order system, repair sites and the accessory warehouse WMS, with updates per order or daily. The document comparison task checks subject, object, status and validity scope across these materials.
At the tool-call and plugin step, the inputs are the text fields and structured fields of those materials. A tool description states the purpose, the input conditions and the situations in which the tool should not be called. Tool parameters divide into fixed parameters for system modules and configurable parameters for plugins. When a required parameter has no suitable value, the model may not call the tool, and prompt wording can guide the user to supply the value.
Constraints at the tool calls step
Tool calls let the model decide from context semantics whether to call a tool. A tool without parameters is judged from its description alone. Among tools with parameters, one whose parameters are not required may still be called, and the model sometimes fabricates a parameter value. When a required parameter has no suitable value, the model may not call the tool. In advanced orchestration, available tools are connected to the tool call module; after connection, tool inputs separate automatically from ordinary inputs, and the description can be edited to sharpen the call timing. Tuning a small number of tools first is advised.
The tool call termination node forcibly ends the current call. It calls no further tools and does not call the AI to summarize tool results. Custom tool variables extend variable input, giving nodes that are not treated as tool parameters a path to be called. These are existing node capabilities. The fields that can actually be configured and the manual comparison actions remain separate matters.
Hypothetical paper exercise sample: a record in an after-sales ticket system contains the material text "Repair application WX-2024-0312; applicant subject: a brand after-sales service center; object: a robot vacuum under order A-7781; application date: 12 March 2024; application item: repair after inspection or reship of accessories." A second material reads "Inspection report JC-2024-0315; inspection conclusion: mainboard fault, mainboard replacement recommended; report date: 15 March 2024." The draft sentence to be assessed is: "The reship for this order is complete and the accessory outbound order has been synchronized." No material supports the completion of the reship or the synchronization of the outbound order, so the sentence is unsupported.
Configuration and implementation checks
| Configuration item | Hypothetical starting point for this exercise | Reason for the choice and comparison method |
|---|---|---|
| Tool description | State that the tool compares subject and status across repair applications, reship orders, inspection reports and accessory outbound orders | Based on the documented purpose of a tool description; compare whether the model selects this tool in a material-comparison context in actual call records |
| Tool parameters | Set material type, document number and date range as configurable plugin parameters | Plugin parameters are documented as configurable; compare the parameter description with the values actually passed |
| Required parameter | Set the document number as a required parameter | The documentation states the model may not call the tool when a required parameter is missing; compare whether non-call records appear when the document number is absent |
| Tool connection | Connect only the material comparison plugin and the termination node | The documentation advises tuning a small number of tools; compare whether call records become more concentrated as the number of connections changes |
| Tool call termination | Place it after the material comparison plugin | The documentation states the termination node ends the current call and does not call the AI for summarization; compare whether later tool call records appear after termination |
| Custom tool variable | Add a parameter description for the material type field | The documentation states custom variables extend input; compare whether the node is called accordingly |
Three common errors
- Treating a tool parameter description as an execution assurance. A parameter description explains the meaning of a parameter and does not ensure that the tool is called or that a business action is performed. For the check, input the document number and material type from the hypothetical sample, compare whether the tool appears in the actual call record, and observe that a missing record means the tool was not called.
- Treating a retrieval result as an authorization status. The same-vector-model requirement for a retrieval library constrains only the association condition and does not constitute permission or entity isolation. For the check, input order number A-7781 from the hypothetical sample, compare whether the returned materials belong to that order, and observe that materials from another order mean the association condition is not met.
- Treating a draft sentence or pending item as a completed fact. In the hypothetical sample the draft sentence states that the reship is complete and the outbound order is synchronized, while the materials contain no accessory outbound order. For the check, input the draft sentence and the existing material list, compare whether an outbound order record exists, and observe that no corresponding record means the sentence is unsupported.
How to verify the setup
- Input the repair application and inspection report text from the hypothetical sample. Compare whether the material comparison plugin appears in the tool call record. The condition is met when the record shows a call to that plugin; when it does not appear, record the result as not called.
- Input the draft sentence and the material list from the hypothetical sample. Compare "reship complete" and "outbound synchronized" in the draft sentence with whether an accessory outbound order exists in the materials. Observe that no outbound order record means the sentence is unsupported; if an outbound order is added later, compare again.
- Input order number A-7781 from the hypothetical sample. Compare whether all returned materials belong to that order. Observe that materials from another order mean the association condition is not met; when the result is empty, check the downstream design against a paper input of an empty list, and do not claim that a fictional rule necessarily returns an empty list.
All checks above are paper reasoning and were not executed. The behavior after tool call termination and the actual call effect of custom variables depend on actual run records.