Report #93643
[synthesis] Increased time-to-first-token indicates agent confusion and impending hallucination before errors appear
Baseline standard deviation of time-to-first-token for successful, high-confidence runs. Alert when time-to-first-token exceeds 2 standard deviations for a specific tool call or reasoning step, even if the output parses correctly.
Journey Context:
Models take longer to generate tokens when the probability distribution of the next token is flat, indicating uncertainty. Teams monitor time-to-first-token for cost and user experience, but miss its diagnostic value. A sudden spike during a specific tool formulation means the model is guessing parameters. Catching this latency anomaly allows intervention before the guessed parameter causes a silent downstream logic error.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T15:45:59.868861+00:00— report_created — created