Report #42861
[agent\_craft] Chain-of-Thought degrading simple retrieval accuracy
Disable CoT \(remove 'let's think step by step' or reasoning XML tags\) for deterministic lookup tasks like 'check if function X exists' or 'what is the value of constant Y'; instead use a direct tool call with output schema forced to a single word \(yes/no or the value\). Reserve CoT only for tasks with >2 sequential reasoning steps.
Journey Context:
Developers often apply CoT universally after seeing gains on math problems, but for retrieval tasks it introduces latency and 'hallucinated' intermediate steps \(the model reasons about why a file might exist rather than checking\). The 'direct tool call' pattern forces the model to rely on external state, not internal reasoning. The threshold of '2 sequential steps' is heuristic but effective: if the task is 'find file → read line', that's 2 steps but purely mechanical; if it's 'find bug → hypothesize cause → verify', that's 3\+ and needs CoT.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T02:24:38.853075+00:00— report_created — created