PR comments, toc fixed

Author: yousefi-msft

articles/microsoft-discovery/concept-discovery-tools.md

@@ -22,21 +22,24 @@ Tools allow agents to perform specific operations in a repeatable, consistent, a
 - **Visualization tools** interpret scientific data or engineering design data and communicate findings graphically. These tools transform data into graphical representations like charts, graphs, and 3D models, making it easier to explore models, identify patterns, and uncover trends and anomalies.
 
 ## Tool types
-Microsoft Discovery supports two types of tools: **action** and **code-based** tools.
+Microsoft Discovery supports two types of tools: **action** and **code-environment based** tools.
 
 ### Action-based tools
 
-Action-based tools are used when the software requires an operating system, such as with commercial, proprietary, or open-source packages. These packages are commonly distributed as binaries or have complex installation requirements. This can include simulators, emulators, compilers, visualizers, linters, design automation tools, modeling packages, and similar complex software packages.
+Action-based tools are used when the software requires an operating system, such as with commercial, proprietary, or open-source packages. These packages are commonly distributed as binaries or have complex installation requirements. Examples are simulators, emulators, compilers, visualizers, linters, design automation tools, modeling packages, and similar complex software packages.
 
-Tools are installed in a Docker image that is then stored in a container registry. The execution profile of each action the tool should perform, along with arguments, required inputs, and expected outputs, is annotated in the tool's profile. The tool profile's annotations provide the agent with the context of the execution and purpose so that it can effectively plan the invocation.
+Tools are installed in a Docker image that is then stored in a container registry. The execution profile of each action the tool should perform, along with arguments, required inputs, and expected outputs, is annotated in the tool's profile. The tool definition's annotations provide the agent with the context of the execution and purpose so that it can effectively plan the invocation.
 
-### Code-based tools
+### Code-environment based tools
 
-A code-based tool enables a Microsoft Discovery agent to run custom code or generate an on-demand tool. Any language that the controlling agent can generate and a software development kit is accessible can be used.  Code-based tools allow an agent to quickly author and execute code. Novel algorithms or dynamically created tools generated by a model are the most likely target scenarios for code-based tools. 
+A code-environment based tool enables a Microsoft Discovery agent to run custom code or generate an on-demand tool. Any language that the controlling agent can generate and a software development kit is accessible can be used. Code-environment based tools allow an agent to quickly author and execute code. Novel algorithms or dynamically created tools generated by a model are the most likely target scenarios for code-environment based tools. 
+
+### Hybrid tools
+Code-environment and action-based tools can be combined to create a hybrid tool. Hybrid tools combine action-based tools in container images with code-environment tools dynamically generated by the platform's AI capabilities. Hybrid tools create a dynamic execution environment allowing AI models to generate code that is executed in the structured environment of action-based tools.
 
 ## Requirements for authoring tools
 
-Action-based tools must be packaged in a Docker container and stored in a registry accessible to the Microsoft Discovery Supercomputer. A tool profile must be written that has the required specifications. Code-based tools also require a tool profile; however, the associated action is directly running the generated code and little else. 
+Action-based tools must be packaged in a Docker container and stored in a registry accessible to the Microsoft Discovery Supercomputer. A tool definition must be written that has the required specifications. Code-environment based tools also require a tool definition; however, the associated action is directly running the generated code and little else. 
 
 ## Cardinality and execution profile
 

articles/microsoft-discovery/toc.yml

@@ -82,7 +82,7 @@ items:
         items:
           - name: Discovery Tool concepts
             href: concept-discovery-tools.md
-            displayName: Discovery Tool, code-based tools, action-based tools
+            displayName: Discovery Tool, code-environment based tools, action-based tools
   - name: How-tos
     items:
       - name: Migration