{"version":"2.1.274","anchor":"tool-result-pairing-repair-now-detects-and-reports-misplace","canonical_anchor":"tool-result-pairing-repair-now-detects-and-reports-misplace","heading":"Tool-result pairing repair now detects and reports 'misplaced' tool results","tier":"internal","area":"Tool Use","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274\/e\/tool-result-pairing-repair-now-detects-and-reports-misplace","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274","markdown":"### Tool-result pairing repair now detects and reports 'misplaced' tool results\n\nTool-result repair now detects and reports 'misplaced' tool results in debug output\n\n**What**\n\nThe internal pass that repairs mismatched tool calls and their results now includes a check for tool results that are \"misplaced.\" When this happens, the debug information generated (both in telemetry and in the strict-mode error message) now includes a `misplaced_tool_results=[...]` list for each affected assistant message.\n\n**Why**\n\nThis gives more detail when diagnosing cases where a tool's result got separated from or mismatched with its originating call, making it easier to understand what went wrong in a conversation's transcript.\n\n- Area: Tool Use\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}