How informative is this exception? Should we be wrapping it in a custom exception type with a more descriptive error message? Or does that happen at a higher level in the stack?