Perhaps a reminder - and a reminder to the AI - is necessary.
file_search is the name of the internal vector store search tool only when gpt-4o is selected.
When employing other models, it has the same name as the retired “retrieval” tool had, myfiles_browser.
So you need to not only understand that
- you can’t talk directly to the AI about “files” (for there are no files for it to observe or read, only a search that can return ranked document chunks), but you also
- must instruct the name of the proper search tool that assistant must call upon within its tools section, when you do instruct the AI about how to find new knowledge that it must employ by writing search queries. The wrong tool name will produce an error return the AI may try to disguise.
- assistant still has file_search enabled and you are using beta:v2 headers
The tool also has misinformation for the AI about where the files come from and “automatically included”:
Parts of the documents uploaded by users will be automatically included in the conversation. Only use this tool, when the relevant parts don’t contain the necessary information to fulfill the user’s request.
I also verified that despite specifying "max_num_results": 6 and it appearing in the run steps for assistant, that 19 chunks were returned, the assistants endpoint blowing through the gpt-4-turbo budget I wanted to spend to replicate any issues. Avoid the malfunctioning Assistants endpoint entirely.
