Report #30316
[cost\_intel] Why does o1-preview fail at calling REST APIs despite being 'smarter'?
Use instruct models \(4o/sonnet\) for tool use and function calling; reserve reasoning for planning the tool sequence, not executing individual calls.
Journey Context:
Reasoning models tend to over-interpret tool schemas, hallucinate parameters, or get stuck in 'analysis paralysis' when the tool description is ambiguous. Instruct models follow the 'happy path' better for structured execution. The pattern is: reasoning model generates the plan \(which tools in which order\), instruct model executes the JSON-RPC calls with strict schema adherence. This separation of concerns prevents the reasoning model from 'thinking' about HTTP headers when it should just be generating JSON.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T05:16:16.334040+00:00— report_created — created