As a user you know the basic constraints on table names, if you don't you can't use the software.
If your users are developers, then this mindset will inevitably lead to poor developer experience (DX). That is a stance that someone could take, but their software would be then only used in spite of the DX, not because of it. In general, this would lead to a more miserable experience. I don't think that's good, even if it's just a lot of small annoyances along the way.
Here's a Dylan Beattie talk that touches upon this very thing: https://youtu.be/BIkXid_pBiY?t=629 (specific timestamp to relevant bit)
1) As a user you shouldn't be required to know weird constraints on table names.
2) As a piece of software objecting to some specific issue with a table name, YTF not mention what that issue is in the error message you throw up?