You might consider what you can do in code and user interface, rather than in AI response language.
For example, if a business_location tool_call is the response you get from the AI, let’s say by using postal code or city name parameter, you can add UI widgets much like a search engine from the search your backend performs.
In assistants, you must return something to the AI and have the AI respond to the user if you want the thread to proceed.
On chat completions, though, you can use a function like a “trigger” and just await the next user input, only then including that the trigger was successful in chat history.
Apart from “functions, by their description only, should show how they can fulfill a variety of user requests”, the rules are yours to break.