The AI is given a myfiles_browser tool, to which it can write search query language. It is a good idea to inform the AI what the myfiles_browser tool will return when what is in the vector store is part of the assistants behavior and operation.
However, utilization is simply that the AI is presented with the ability to write a search query, and the chunks that are most similar to what is written are returned. It cannot explore.
The top-ranked chunks have the source file and an index number after they come back. However, the AI has no way to specify or explore a subdomain of documents.
Therefore:
- “recognize the file tree” doesn’t have much meaning.
If the user is the one adding documents, which are returned by the same search query as any other vector stores in operation, then I can see it being a good idea to amend the AI’s knowledge. The file name alone, such as a post-prompt automatically added to a message “[I uploaded 2835.385.pdf]” might be a good idea to ‘activate’ more searching.
However, you can see that file name alone could be less than useful. Imagine:
- if your user interface uploader also had a dialog that asked for “Contents: (what’s in the document you are adding)”. Forcing it to be spelled out by the user, and not relying on the user input to mention the file, might improve the searching, but could be cumbersome.