Report #68508
[agent\_craft] Agent selects expensive search tools when simple file reading suffices
Implement a 'Tool Complexity Ladder' in the system prompt: 'Step 1: Check current file. Step 2: Check explicitly imported files. Step 3: Use codebase search only if Steps 1-2 fail.' Enforce this via explicit step-by-step scratchpad.
Journey Context:
Agents often default to the most powerful \(and expensive/latent\) tool available, such as semantic search or grep over the entire codebase, when the required information is in the current working file. This is a 'greedy' selection strategy that wastes tokens and increases latency. The Complexity Ladder enforces 'Occam's Razor' for tool use: prefer the simplest sufficient tool. This is critical for cost-effective agent operation and prevents 'over-tooling' where the agent uses a sledgehammer to crack a nut.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T21:28:36.916613+00:00— report_created — created