[frostming]

Adds a "Use built-in tools" section to docs/guides/tools.md, between the function and native tool sections.

• Example using WebSearch with allowed_domains and UserLocation, reading response.citations and response.builtin_tool_calls
• Support table for WebSearch, WebFetch, CodeExecution, and ImageGeneration across the responses, messages, gemini, and chat API formats
• Where results appear (builtin_tool_calls, citations, image_parts) and the matching stream events
• Continuing a turn that ends with finish_reason == "pause"

The paragraph on provider-run tools at the end of the function tools section moves into the new section.

🤖 Generated with Claude Code

[github-actions]

No blocking findings. The support table matches what each format accepts or rejects, the example's request mapping is correct, and the pause loop correctly round-trips the server tool blocks. Two documentation accuracy issues are noted inline: the citations claim does not hold for Gemini web fetch, and the pause snippet depends on names that are not in scope.

[github-actions]

No blocking findings.

The new section's claims hold at the current head: the support table matches each format's mapping and rejections (chat accepts only WebSearch and rejects max_uses/domain settings, responses rejects max_uses/blocked_domains, messages accepts all four it lists except image generation, gemini rejects any setting), both examples run as written, and the pause loop submits the paused assistant turn back with server_tool_use/web_search_tool_result intact.

Both findings from the previous review are repaired in df54609: the citations sentence is scoped and points Gemini users to builtin_tool_calls (thread), and the continuation snippet now defines its prompt and states that model/search come from the example above (thread).