Report #91795
[architecture] Wrapping simple API calls or deterministic functions as independent agents
If a component has no LLM, no autonomous decision-making, and no internal state, implement it as a tool/function, not an agent.
Journey Context:
A common anti-pattern is creating a 'Database Agent' or 'API Agent' that merely formats a query and returns a result. This introduces unnecessary LLM calls, latency, and hallucination risk for deterministic work. An agent implies autonomy, planning, and the ability to handle ambiguity. If the step is deterministic or a simple API translation, it must be a tool executed by a real agent. Over-agentizing increases coordination overhead and degrades reliability.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T12:40:09.415064+00:00— report_created — created