InputValidationError should universally include the failing field + expected shape

Context: solo owner running Claude Code across 4 projects with autonomous ticket-runner sessions (~1000 session transcripts / 17 days; systematic transcript audit). macOS, CLI + VSCode extension.

When a tool call fails schema validation (AskUserQuestion is the frequent one for us), the error historically didn't say which parameter was wrong, producing blind retry loops (worst observed: 7 identical failures in a row before a fallback). We now pre-validate via a PreToolUse hook, but the native error could carry the same information.

Ask: include the failing field + expected shape in InputValidationError (some newer errors already do this — making it universal would remove the failure mode).

Happy to share sanitized transcript excerpts.