It is tempting, maybe a good first step, but often not expressive enough.

Especially and particularly attributes/fields/properties in an enterprise solution.

You want to associate various metadata - including at runtime - with a _value_ and use that as attribute/field/property in a container.

You want to be able to transport and combine these values in different ways, especially if your business domain is subject to many changes.

If you are tempted to use "classes" for this, you will sign up for significant pain later down the road.