docs: clarify synthesized web search count behavior

docs/tools/gemini-search.md

@@ -76,7 +76,12 @@ URLs.
 
 ## Supported parameters
 
-Gemini search supports the standard `query` and `count` parameters.
+Gemini search supports `query`.
+
+`count` is accepted for shared `web_search` compatibility, but Gemini grounding
+still returns one synthesized answer with citations rather than an N-result
+list.
+
 Provider-specific filters like `country`, `language`, `freshness`, and
 `domain_filter` are not supported.
 

docs/tools/grok-search.md

@@ -88,7 +88,11 @@ citations, similar to Gemini's Google Search grounding approach.
 
 ## Supported parameters
 
-Grok search supports the standard `query` and `count` parameters.
+Grok search supports `query`.
+
+`count` is accepted for shared `web_search` compatibility, but Grok still
+returns one synthesized answer with citations rather than an N-result list.
+
 Provider-specific filters are not currently supported.
 
 ## Related

docs/tools/kimi-search.md

@@ -83,7 +83,11 @@ similar to Gemini and Grok's grounded response approach.
 
 ## Supported parameters
 
-Kimi search supports the standard `query` and `count` parameters.
+Kimi search supports `query`.
+
+`count` is accepted for shared `web_search` compatibility, but Kimi still
+returns one synthesized answer with citations rather than an N-result list.
+
 Provider-specific filters are not currently supported.
 
 ## Related

docs/tools/web.md

@@ -271,6 +271,9 @@ show the `x_search` prompt.
 <Warning>
   Not all parameters work with all providers. Brave `llm-context` mode
   rejects `ui_lang`, `freshness`, `date_after`, and `date_before`.
+  Gemini, Grok, and Kimi return one synthesized answer with citations. They
+  accept `count` for shared-tool compatibility, but it does not change the
+  grounded answer shape.
   Firecrawl and Tavily only support `query` and `count` through `web_search`
   -- use their dedicated tools for advanced options.
 </Warning>