diff --git a/docs/tools-custom/function-tools.md b/docs/tools-custom/function-tools.md
index 4a47cad74..172500031 100644
--- a/docs/tools-custom/function-tools.md
+++ b/docs/tools-custom/function-tools.md
@@ -423,7 +423,7 @@ To use an agent as a tool, wrap the agent with the AgentTool class.
 === "Python"
 
     ```py
-    tools=[AgentTool(agent=agent_b)]
+    tools=[AgentTool(agent=agent_b, include_plugins=True)]
     ```
 
 === "Go"
@@ -444,6 +444,7 @@ To use an agent as a tool, wrap the agent with the AgentTool class.
 The `AgentTool` class provides the following attributes for customizing its behavior:
 
 * **skip\_summarization: bool:** If set to True, the framework will **bypass the LLM-based summarization** of the tool agent's response. This can be useful when the tool's response is already well-formatted and requires no further processing.
+* **include\_plugins: bool:** If set to True (the default), plugins from the parent runner are propagated to the agent's runner. This means the agent inherits all plugins from its parent. Set to False to run the agent with an isolated plugin environment.
 
 ??? "Example"
 
@@ -481,4 +482,4 @@ The `AgentTool` class provides the following attributes for customizing its beha
 3. Behind the scenes, the `main_agent` will call the `summary_agent` with the long text as input.  
 4. The `summary_agent` will process the text according to its instruction and generate a summary.  
 5. **The response from the `summary_agent` is then passed back to the `main_agent`.**  
-6. The `main_agent` can then take the summary and formulate its final response to the user (e.g., "Here's a summary of the text: ...")
+6. The `main_agent` can then take the summary and formulate its final response to the user (e.g., "Here's a summary of the text: ...")
\ No newline at end of file