docs: clarify tool search support and namespace guidance#1072
Merged
Conversation
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request updates the tool search documentation to align the JS SDK guides with the current Responses API behavior and the official tool search guide. It adds a new docs example for deferred tool loading, explains when to keep a deferred tool top-level versus grouping related tools with
toolNamespace(), and documents that namespaced and top-level deferred tools can be mixed in the same request.It also fills in the supporting guide coverage around tool search by:
tool_searchandtoolSearchTool()to the main tools guideRunToolSearchCallItem/RunToolSearchOutputItemresult surfacestool_search_called/tool_search_output_createdstreaming events