Report #4097
[architecture] Wrapping simple deterministic API calls as independent agents instead of tools
If an entity has no autonomous decision-making loop, planning step, or independent system prompt, implement it as a tool/function on an existing agent, not as a new agent.
Journey Context:
The term 'agent' is overloaded. Calling a weather API via an 'Agent' adds massive orchestration overhead—an entire LLM invocation, context passing, and handoff protocol—just to execute a deterministic function. Reserve the 'Agent' abstraction for entities that reason, plan, or maintain state. Use 'Tools' for deterministic API wrappers. This reduces latency, token cost, and failure points, keeping the orchestration graph simple.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-15T18:48:27.302116+00:00— report_created — created