From 09b98576b1c816a425b8b90376280c5a592c9342 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=E5=86=AF=E5=9F=BA=E9=AD=81?= <1412414664@qq.com>
Date: Mon, 8 Jun 2026 13:24:16 +0800
Subject: [PATCH] docs: clarify test connection model precedence

---
 litellm/proxy/health_endpoints/_health_endpoints.py | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/litellm/proxy/health_endpoints/_health_endpoints.py b/litellm/proxy/health_endpoints/_health_endpoints.py
index bf7e3eba048..fd504c8d53a 100644
--- a/litellm/proxy/health_endpoints/_health_endpoints.py
+++ b/litellm/proxy/health_endpoints/_health_endpoints.py
@@ -1843,7 +1843,9 @@ async def test_model_connection(
     Note: 
     - If the model is configured in proxy_config.yaml, credentials (api_key, api_base, etc.) 
       will be automatically loaded from the config (with resolved environment variables).
-    - You can override specific params by including them in the request.
+    - You can override specific params by including them in the request. If the
+      model is configured in proxy_config.yaml, the configured provider model is
+      used for the connection test.
     - You can use `os.environ/VARIABLE_NAME` syntax to reference environment variables,
       which will be resolved automatically (same as in proxy_config.yaml).