diff --git a/process/process_areas/quality_management/guidance/quality_review_checklist.rst b/process/process_areas/quality_management/guidance/quality_review_checklist.rst
index 6fd1d6c8d5..e08df7d4c6 100644
--- a/process/process_areas/quality_management/guidance/quality_review_checklist.rst
+++ b/process/process_areas/quality_management/guidance/quality_review_checklist.rst
@@ -395,9 +395,9 @@ Software Verification plan review checklist template
           - Check if the software quality criteria are clearly defined and understood by all relevant parties. Have a look on the reports to verify if the criteria are fulfilled.
           -
         * - SWV_00_05
-          - Are all used tools described?
+          - Are all used tools described and included in the project's tool list?
           -
-          - Check if all tools used for software verification are clearly described and used as defined. Are additional tools used that are not described?
+          - Check if all tools used for software verification are clearly described, listed in the project's tool list, and used as defined. Are additional tools used that are not described or missing from the project's tool list?
           -
         * - SWV_00_06
           - Are verification setups and variants described, documented and up to date?
@@ -452,7 +452,7 @@ Software Development Plan review checklist template
           - Check if the software configuration guideline is followed and if deviations have an approved argumentation by the CODEOWNER.
           -
         * - SDP_00_05
-          - Are all SW development tools described?
+          - Are all SW development tools described and included in the project's tool list?
           -
-          - Check if all tools used for software development are clearly described. If possible check if they are used as defined.
+          - Check if all tools used for software development are clearly described and listed in the project's tool list. If possible check if they are used as defined.
           -
diff --git a/process/process_areas/requirements_engineering/requirements_workflow.rst b/process/process_areas/requirements_engineering/requirements_workflow.rst
index e98e9f9e1f..703756de5b 100644
--- a/process/process_areas/requirements_engineering/requirements_workflow.rst
+++ b/process/process_areas/requirements_engineering/requirements_workflow.rst
@@ -101,7 +101,7 @@ For a detailed explanation of workflows and their role within the process model,
    :contains: gd_temp__req_process_req, gd_temp__req_tool_req, gd_temp__req_formulation
    :has: doc_concept__req_process, doc_getstrt__req_process
 
-   Based on the process descriptions (which comply to standards) and/or stakeholder requirements process and tool requirements are derived.
+   Based on the process descriptions (which comply to standards) and/or stakeholder/feature/component requirements process and tool requirements are derived.
 
 .. workflow:: Monitor/Verify Requirements
    :id: wf__monitor_verify_requirements
diff --git a/process/process_areas/tool_management/tool_management_workflow.rst b/process/process_areas/tool_management/tool_management_workflow.rst
index 24265829c1..9c142803f9 100644
--- a/process/process_areas/tool_management/tool_management_workflow.rst
+++ b/process/process_areas/tool_management/tool_management_workflow.rst
@@ -42,13 +42,14 @@ For a detailed explanation of workflows and their role within the process model,
    :responsible: rl__contributor
    :approved_by: rl__committer, rl__safety_manager, rl__security_manager
    :supported_by: rl__infrastructure_tooling_community
-   :input: wp__tool_verification_report
+   :input: wp__tool_verification_report, wp__requirements_stkh, wp__requirements_feat, wp__requirements_comp, wp__requirements_proc_tool
    :output: wp__tool_verification_report
    :contains: gd_temp__tool_management_verif_rpt_template, gd_chklst__tool_cr_review
    :has: doc_concept__tool_process, doc_getstrt__tool_process
 
    Each identified tool is evaluated. During evaluation the Tool Verification Report
-   is updated accordingly.
+   is updated accordingly. Stakeholder, feature, component, and process/tool
+   requirements may be used as input for the tool evaluation and verification.
    After successful evaluation the status of the Tool Verification Report
    is set to evaluated.