Report #90159
[synthesis] Tool calls failing due to hallucinated or missing current date/time parameters
Always inject the current UTC datetime into the system prompt, and explicitly reference it in the tool description: 'The current time is provided in the system prompt; use it for this parameter.'
Journey Context:
When a tool requires a timestamp, GPT-4o frequently hallucinates a date based on its training data cutoff. Claude 3.5 often refuses to guess the date, resulting in a tool call refusal or placeholder string. Gemini attempts to use internal state but formats inconsistently. Assuming models 'know' the current time causes silent, hard-to-trace data integrity errors in time-sensitive tool calls \(e.g., scheduling, logging\). The only cross-model defense is injecting the time and forcing the model to read it via the tool description.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T09:55:40.804295+00:00— report_created — created