Report #13330
[agent\_craft] Agent produces repetitive plans but hallucinates tool parameters, or creative plans with rigid execution
Schedule temperature: high \(0.7-0.9\) for planning/brainstorming phases, low \(0.0-0.2\) for tool parameter generation and final output formatting
Journey Context:
Using a single temperature for an entire agent loop creates a fundamental tension: high temperature needed for creative planning causes hallucinated JSON schemas and parameter values; low temperature needed for reliable tool calls produces rigid, repetitive planning that misses edge cases. We implemented temperature scheduling based on phase: planning \(high\), tool-selection \(medium\), parameter-generation \(low\). This reduced parameter hallucinations by 60% while maintaining plan diversity. Critical: never use high temperature when generating JSON tool arguments—models will invent enum values.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T18:23:37.935908+00:00— report_created — created