{"version":"2.1.280","anchor":"tool-call-input-validation-now-tracks-coercion-diagnostics","canonical_anchor":"tool-call-input-validation-now-tracks-coercion-diagnostics","heading":"Tool-call input validation now tracks coercion diagnostics (shapeClass\/valid\/resultNote)","tier":"internal","area":"Elsewhere","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/tool-call-input-validation-now-tracks-coercion-diagnostics","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Tool-call input validation now tracks coercion diagnostics (shapeClass\/valid\/resultNote)\n\nTool-call input auto-repair now records structured diagnostics instead of a plain pass\/fail\n\n**What**\n\nWhen Claude Code auto-repairs (coerces) a tool call's raw input before checking it against the tool's expected schema, it now records structured diagnostics about that repair: a `shapeClass` describing the input's shape, whether the repaired input actually passed validation, and a `resultNote` with more detail.\n\n**Why**\n\nThis gives more precise information about why a tool call's input needed fixing, instead of only a simple pass\/fail result, which should help diagnose tool-input problems.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}