Report #3866
[agent\_craft] Unconditionally appending 'Let's think step by step' increases latency, token cost, and can introduce hallucinations for simple retrieval or single-step tasks
Use Chain-of-Thought \(CoT\) only for tasks requiring multi-step reasoning, arithmetic, or debugging; use direct instruction for simple lookups or deterministic transformations
Journey Context:
CoT is powerful but not free. For tool lookups \('get weather'\) or simple string formatting, forcing reasoning steps adds noise and latency. The sophisticated pattern is conditional CoT: trigger explicit reasoning only when confidence is low, the task is multi-step, or the user asks 'why'. This optimizes for both accuracy and efficiency.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-15T18:21:05.911546+00:00— report_created — created