Properties are the CRM's columns, and every one somebody adds is one everybody else has to understand. Create a custom property when no default property fits, with a clear label, a stable internal name (the value imports and integrations use, which never changes), the right field type and a group that keeps the record readable.
Choose the type for how the property will be used: a number to compare, a dropdown for a fixed list, a date to filter on.
Retiring a property is the other half. Archive it once nothing depends on it: here, archiving is blocked while a list, workflow, form or report uses the property, and the Properties page shows where each one is used. Remove those uses first.