If Jev picks the tool, how does the LLM ask for another one?

I’ve been looking at how people are using Jev for tool selection in agents. One pattern I keep seeing is: Jev picks the next tool → only that tool schema is exposed → LLM generates the args → tool executes That makes sense from a context/cost point of view, but I’m curious about the agent loop after that. Say the agent knows at a high level that it has docs, email, calendar, etc tools (placed inside the system prompt). Jev exposes write_document, and the agent creates the doc. Now the agent thinks, “I should offer to email this too.” It knows email capability exists, but it doesn’t have the email tool schema because Jev is the one deciding what gets exposed. So how are people handling that handoff? Do you: give the agent something like find_tool / get_tool_schema so it can request a capability when needed? let Jev run again after every tool call and decide the next tool? expose a small top-K set of tools instead of just one? keep the full capability catalog visible to the LLM, but dynamically inject schemas only when needed? The part I’m trying to understand is where the planning responsibility should sit. If Jev keeps deciding the next action every loop, it starts becoming the policy/controller for the agent. But if the LLM is still supposed to plan multiple steps ahead, it needs some way to pull in tools it knows exist but doesn’t currently have schemas for. Curious how others are designing this in real implementations.