Truncated tool call: a 200 OK that cut the arguments off mid-JSON
An agent tool call truncated by max_tokens arrives as HTTP 200 with incomplete JSON. Which stop reason to check on Claude and OpenAI, and how to retry.
The layer agents reach through: protocols, connectors, sandboxes and the maintenance they demand.
An agent tool call truncated by max_tokens arrives as HTTP 200 with incomplete JSON. Which stop reason to check on Claude and OpenAI, and how to retry.
Retrying a tool call after a timeout duplicated the side effect in up to 76% of simulated runs. How idempotency keys and verify-before-retry stop it.
Summary, note file, retrieval index and prompt cache solve different problems. Teams pick one, use it for everything, and pay for the mismatch every turn.
Constrained decoding made malformed tool arguments rare. It did nothing for wrong ones, and most pipelines still read a parsed object as a correct one.
Vendor cold starts for agent sandboxes span 25ms to 150ms. An independent 2026 benchmark measured 0.27s to 5.06s. Which of the two should decide.
Langfuse, LangSmith, Braintrust, Phoenix and Helicone priced side by side. The deciding factor is usually where your traces are allowed to live.
Accuracy falls as context grows, across every model tested. Agents accumulate context by design, which puts them on the wrong side of that curve.
MCP hit 41% production adoption before it had a trust model. Scans find 30 to 82% of public servers flawed and 8.5% using OAuth.
OpenTelemetry's GenAI conventions put token usage on every span. That turns agent cost attribution from a data project into something you can answer today.