diff --git a/metagpt/actions/requirement_analysis/framework/evaluate_framework.py b/metagpt/actions/requirement_analysis/framework/evaluate_framework.py
index 74f8a024a..d0aaf012c 100644
--- a/metagpt/actions/requirement_analysis/framework/evaluate_framework.py
+++ b/metagpt/actions/requirement_analysis/framework/evaluate_framework.py
@@ -97,9 +97,10 @@ Do not implement the interface in "Acknowledge" section until it is used in "Leg
 Parts not mentioned in the "Legacy TRD" will be handled by other TRDs, therefore, processes not present in the "Legacy TRD" are considered ready;
 "Additional Technical Requirements" specifies the additional technical requirements that the generated software framework code must meet;
 Do the parameters of the interface of the external system used in the code comply with it's specifications in 'Acknowledge'?
+Is there a lack of necessary configuration files?
 Return a markdown JSON object with:
 - a "is_pass" key containing a true boolean value if there is not any issue in the "Legacy Outputs";
-- an "issues" key containing a string list of natural text about the issues found in the "Legacy Outputs" if any, each issue found must provide a detailed description and include reasons;
+- an "issues" key containing a string list of natural text about the issues that need to addressed, found in the "Legacy Outputs" if any exits, each issue found must provide a detailed description and include reasons;
 - a "conclusion" key containing the evaluation conclusion;
 - a "misalignment" key containing the judgement detail of the natural text string list about the misalignment with "Legacy TRD";
 """
diff --git a/metagpt/actions/requirement_analysis/trd/evaluate_trd.py b/metagpt/actions/requirement_analysis/trd/evaluate_trd.py
index 7feb32112..5fc1ca06c 100644
--- a/metagpt/actions/requirement_analysis/trd/evaluate_trd.py
+++ b/metagpt/actions/requirement_analysis/trd/evaluate_trd.py
@@ -105,9 +105,10 @@ If the descriptions in "User Requirements" are divided into multiple steps in "T
 There is a possibility of missing details in the descriptions of "User Requirements". Any additional steps in "TRD Design" and "Interaction Events" are considered compliant with "User Requirements" as long as they do not conflict with the descriptions provided in "User Requirements";
 If there are interaction events with external systems in "TRD Design", you must explicitly specify the ID of the external interface to use for the interaction events;
 Does the sequence of steps in "Interaction Events" cause performance or cost issues? Please provide detailed descriptions and reasons;
+It is problematic if the data stream composed of input/output contains passive or irrelevant data;
 Return a markdown JSON object with:
 - a "is_pass" key containing a true boolean value if there is not any issue in the "TRD Design";
-- an "issues" key containing a string list of natural text about the issues found in the "TRD Design" if any, each issue found must provide a detailed description and include reasons;
+- an "issues" key containing a string list of natural text about the issues that need to be addressed, found in the "TRD Design" if any exist, each issue found must provide a detailed description and include reasons;
 - a "conclusion" key containing the evaluation conclusion;
 - a "correspondence_between" key containing the judgement detail of the natural text string list about the correspondence between "Interaction Events" and "TRD Design" steps;
 - a "misalignment" key containing the judgement detail of the natural text string list about the misalignment with "User Requirements";
diff --git a/tests/data/requirements/1.constraint.md b/tests/data/requirements/1.constraint.md
index b8c42be63..576df59bf 100644
--- a/tests/data/requirements/1.constraint.md
+++ b/tests/data/requirements/1.constraint.md
@@ -1,3 +1,4 @@
-- 用javascript语言, 法务查询者与国际小超人钉钉小程序之间UI用web；
+- Using pure javascript without any third-party package, 法务查询者与国际小超人钉钉小程序之间UI用web；
 - 法务中台网址：`https://mock.apipark.cn/m1/4717294-4369585-default`;
-- 写代码时，不要单元测试代码;
\ No newline at end of file
+- 写代码时，不要单元测试代码;
+- 如果使用了接口 ID 6, 它的返回结果要去重复项;
\ No newline at end of file