What this category's data looks like
This category covers three types of materials: business cooperation agreements, advertising review forms, and distribution cooperation materials. A business cooperation agreement contains the partner name, cooperation period, revenue-sharing ratio, and signature field; an advertising review form contains the advertiser name, issue number, advertising content, review opinion, signature, and receipt; distribution cooperation materials contain the distribution channel name, quantity, start and end dates, and receipt records. The materials come from submissions by business departments and system archiving, updated weekly and summarized at month-end. When entering this feature, the tool call node is responsible for initiating query and verification calls by material field, returning inputs and return values; the progress table and statistical scope description are completed by subsequent AI nodes or manually. During verification, the three types of materials serve as references for one another, and names, quantities, dates, and signatures must be consistent across materials.
Configuration and implementation checks
This step is executed by the tool call node in the workflow (the model decides whether to call it, and the node executes it), outputting the tool call result (the inputs and returns in the call record). The "progress table and statistical scope description" is then completed by subsequent AI nodes or manual verification. Based on the tool description, parameter descriptions, and whether parameters are required, the model determines whether to call the tool this time.
| Object | Check | Verification action |
|---|---|---|
| Business cooperation agreement | Whether the partner name, cooperation period, revenue-sharing ratio, and signature field correspond to the advertising review form and distribution cooperation materials | Open the tool node description field and check whether the description can be understood on its own; run a trial with a question missing a required parameter to see whether it asks a follow-up question; check the values of toolChoice and functionCall in the call record |
| Advertising review form | Whether the advertiser name, issue number, review opinion, signature, and receipt are consistent with the business cooperation agreement and distribution cooperation materials | Open each parameter configuration one by one and check the parameter description and whether it is required; run a trial with a question missing the advertiser name to see whether the return fabricates a nonexistent value |
| Distribution cooperation materials | Whether the distribution channel name, quantity, start and end dates, and receipt records match the business cooperation agreement and advertising review form | Check the diamond-shaped connections and node status on the canvas; check whether results are mixed up after multiple tools are chained; record the inputs and returns in the call record |
| Progress table and statistical scope description | Whether the record count and statistical count match, whether the scope is written in the header, and whether exceptions are clearly stated | Use one week of records to verify the total and see whether the scope and exceptions are clearly stated; check the tokens of the referenced text, and record the number of array items separately |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match between the business cooperation agreement and the advertising review form. Cause: The two materials are entered separately, without cross-material field comparison and receipt verification.
- Symptom: The version of the distribution cooperation materials is not synchronized, and the old quantity is mixed with the new date. Cause: After the materials are updated, they are not synchronized to the data source referenced by the tool call node, and the call returns the old value.
- Symptom: The advertising review form lacks a signature or receipt, but the call still returns completed. Cause: Marking a parameter as required does not guarantee that the model will ask a follow-up question; it depends on prompt guidance, and a tool call does not equal scheduled execution.
How to verify the setup
Feature acceptance: run a trial with a question missing a required parameter, check the inputs and returns in the call record, and confirm whether it asks a follow-up question or calls according to the description; check the values of toolChoice and functionCall in the record, check the tokens of the referenced text, and record the number of array items separately.
Business testing: use one week of records to verify the total, see whether the scope and exceptions are clearly stated, confirm that the record count and statistical count match, and that the scope is written in the header.
- Open the tool node description field, check whether the description can be understood when taken out on its own, check the two items of parameter description and whether it is required, and run a trial with a question missing that field to see whether it asks a follow-up question first.
- Check the diamond-shaped connections and node status on the canvas, check whether results are mixed up after multiple tools are chained, and record the inputs and returns in the call record one by one.