When you create a database table its purpose and context is obvious for you, so often you don't put too much thought into naming. But... sometime later you may have no idea what this table is used for or be able to find it. Other people are n an even worse situation.
Therefore - I advocate into putting an emphasis on meaningful names of tables and columns. It can have potentially a lot of consumers throughout its lifetime. And changing name in the future is close to impossible.
If you'd look at some database designs - list of their table and column names - you might think you're looking at hieroglyphs. Behind those cryptic texts are hidden business entities that are relevant to you, such as customers, orders, products, etc. Do your organization and data teams a favor - translate this ancient writing into human speak!
You can do this be creating and sharing a data dictionary with aliases and descriptions. There's a perfect tool for this - Dataedo.