Report #44918
[architecture] Creating a new agent for a simple API call or deterministic computation
If the task is deterministic, stateless, and requires no LLM reasoning, implement it as a tool/function on an existing agent, not as a standalone agent.
Journey Context:
The term 'agent' implies an LLM making reasoning loops. Spinning up an agent to do a math calculation, fetch a URL, or query a SQL database wastes tokens, adds latency, and introduces non-determinism where none is needed. Agents are for reasoning and planning; tools are for execution. An agent should be a specialized reasoner heavily armed with deterministic tools, not a bare orchestrator delegating deterministic work to other 'agents'.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T05:51:40.983328+00:00— report_created — created