Yes, I understand that.
This is clear for me. But “Invalid Argument” or “Bad Value” is too generic. Is this numeric value not matching expected numeric value? Is it a number instead of object? Or an object of not expected type? Or an object of unknown type? Is it null redeference? Is it an uninitialized object? Is it something different? All these use-cases can be treated as “Invalid Argument” / “Bad Value”, but this is a symptom rather than the cause of the problem.
I let CLISP developers to analyze is possible.