diff --git a/packages/toolbox-adk/README.md b/packages/toolbox-adk/README.md
index bc9b3ea7..8fd432a6 100644
--- a/packages/toolbox-adk/README.md
+++ b/packages/toolbox-adk/README.md
@@ -56,11 +56,10 @@ agent = Agent(tools=[toolset])
 
 The SDK supports multiple transport protocols for communicating with the Toolbox server. By default, the client uses the latest supported version of the **Model Context Protocol (MCP)**.
 
-You can explicitly select a protocol using the `protocol` option during toolset initialization. This is useful if you need to use the native Toolbox HTTP protocol or pin the client to a specific legacy version of MCP.
+You can explicitly select a protocol using the `protocol` option during toolset initialization. This is useful if you need to pin the client to a specific legacy version of MCP.
 
 > [!NOTE]
-> * **Native Toolbox Transport**: This uses the service's native **REST over HTTP** API.
-> * **MCP Transports**: These options use the **Model Context Protocol over HTTP**.
+> * **MCP Transports**: These options use **Model Context Protocol over HTTP**.
 
 ### Supported Protocols
 
@@ -72,11 +71,8 @@ You can explicitly select a protocol using the `protocol` option during toolset
 | `Protocol.MCP_v20250326` | MCP Protocol version 2025-03-26. |
 | `Protocol.MCP_v20241105` | MCP Protocol version 2024-11-05. |
 
-> [!WARNING]
-
 ### Example
 
-
 ```python
 from toolbox_adk import ToolboxToolset
 from toolbox_core.protocol import Protocol
diff --git a/packages/toolbox-core/README.md b/packages/toolbox-core/README.md
index a3c9b474..c85a3e33 100644
--- a/packages/toolbox-core/README.md
+++ b/packages/toolbox-core/README.md
@@ -149,11 +149,10 @@ All interactions for loading and invoking tools happen through this client.
 
 The SDK supports multiple transport protocols for communicating with the Toolbox server. By default, the client uses the latest supported version of the **Model Context Protocol (MCP)**.
 
-You can explicitly select a protocol using the `protocol` option during client initialization. This is useful if you need to use the native Toolbox HTTP protocol or pin the client to a specific legacy version of MCP.
+You can explicitly select a protocol using the `protocol` option during client initialization. This is useful if you need to pin the client to a specific legacy version of MCP.
 
 > [!NOTE]
-> * **Native Toolbox Transport**: This uses the service's native **REST over HTTP** API.
-> * **MCP Transports**: These options use the **Model Context Protocol over HTTP**.
+> * **MCP Transports**: These options use **Model Context Protocol over HTTP**.
 
 ### Supported Protocols
 
@@ -164,11 +163,8 @@ You can explicitly select a protocol using the `protocol` option during client i
 | `Protocol.MCP_v20250618` | MCP Protocol version 2025-06-18. |
 | `Protocol.MCP_v20241105` | MCP Protocol version 2024-11-05. |
 
-> [!WARNING]
-
 ### Example
 
-
 ```py
 from toolbox_core import ToolboxClient
 from toolbox_core.protocol import Protocol
diff --git a/packages/toolbox-langchain/README.md b/packages/toolbox-langchain/README.md
index 7c38841c..6679369c 100644
--- a/packages/toolbox-langchain/README.md
+++ b/packages/toolbox-langchain/README.md
@@ -96,11 +96,10 @@ async with ToolboxClient("http://127.0.0.1:5000") as toolbox:
 
 The SDK supports multiple transport protocols for communicating with the Toolbox server. By default, the client uses the latest supported version of the **Model Context Protocol (MCP)**.
 
-You can explicitly select a protocol using the `protocol` option during client initialization. This is useful if you need to use the native Toolbox HTTP protocol or pin the client to a specific legacy version of MCP.
+You can explicitly select a protocol using the `protocol` option during client initialization. This is useful if you need to pin the client to a specific legacy version of MCP.
 
 > [!NOTE]
-> * **Native Toolbox Transport**: This uses the service's native **REST over HTTP** API.
-> * **MCP Transports**: These options use the **Model Context Protocol over HTTP**.
+> * **MCP Transports**: These options use **Model Context Protocol over HTTP**.
 
 ### Supported Protocols
 
@@ -112,11 +111,8 @@ You can explicitly select a protocol using the `protocol` option during client i
 | `Protocol.MCP_v20250326` | MCP Protocol version 2025-03-26. |
 | `Protocol.MCP_v20241105` | MCP Protocol version 2024-11-05. |
 
-> [!WARNING]
-
 ### Example
 
-
 ```py
 from toolbox_langchain import ToolboxClient
 from toolbox_core.protocol import Protocol
diff --git a/packages/toolbox-llamaindex/README.md b/packages/toolbox-llamaindex/README.md
index eb26862b..844c1964 100644
--- a/packages/toolbox-llamaindex/README.md
+++ b/packages/toolbox-llamaindex/README.md
@@ -100,10 +100,9 @@ async with ToolboxClient("http://127.0.0.1:5000") as toolbox:
 
 The SDK supports multiple transport protocols for communicating with the Toolbox server. By default, the client uses the latest supported version of the **Model Context Protocol (MCP)**.
 
-You can explicitly select a protocol using the `protocol` option during client initialization. This is useful if you need to use the native Toolbox HTTP protocol or pin the client to a specific legacy version of MCP.
+You can explicitly select a protocol using the `protocol` option during client initialization. This is useful if you need to pin the client to a specific legacy version of MCP.
 
 > [!NOTE]
-> * **Native Toolbox Transport**: This uses the service's native **REST over HTTP** API.
 > * **MCP Transports**: These options use the **Model Context Protocol over HTTP**.
 
 ### Supported Protocols
@@ -116,11 +115,8 @@ You can explicitly select a protocol using the `protocol` option during client i
 | `Protocol.MCP_v20250326` | MCP Protocol version 2025-03-26. |
 | `Protocol.MCP_v20241105` | MCP Protocol version 2024-11-05. |
 
-> [!WARNING]
-
 ### Example
 
-
 ```py
 from toolbox_llamaindex import ToolboxClient
 from toolbox_core.protocol import Protocol