An operations agent has access to dozens of tools (ticketing, CMDB, runbooks, paging, metrics). For routine password resets it should call only the identity and ticketing tools; for major incidents it may need metrics, paging, and runbook tools. The team wants the model to choose tools based on the live situation rather than always binding the full catalog into every turn. Which approach best supports this?
Select an answer to reveal the explanation.
Short Explanation
Big tool catalogs confuse models and waste tokens. Dynamic tool use (or specified tool selection per turn) narrows what the agent can see to what the situation needs—password reset vs major incident—while still allowing broader tools when the planner says so. Stuffing every OpenAPI every time is noisy. No tools at all abandons automation. Firing every tool always is expensive and pollutes context. C is the design that matches situational tool needs.
Full Explanation
Correct answer: C. Integrating external resources includes function calling, specified tool use, and dynamic tool use. Dynamic exposure—filtering or retrieving a relevant tool subset based on intent, route, or planner state—improves precision, reduces token overhead, and lowers wrong-tool risk in large catalogs.
A is incorrect because always embedding the full catalog increases prompt size and tool-selection errors.
B is incorrect because removing tools forces manual work and defeats agentic automation.
D is incorrect because invoking every tool every turn is costly, slow, and floods context with irrelevant data.
Exam focus: dynamic/specified tool use scales tool ecosystems without full-catalog binding each turn.