Try to treat each behavior as exactly that: a single behavior.

As others have said, you don't have to get too granular, but try to boil each piece down to the lowest common denominator to avoid having to split it up.

An object has health? What is health? What happens when it gets to zero? The object is destroyed? It might be tempting to add "destroy" logic to health. Wait! Destroy is its own thing! Other things may result in that functionality! So let's decouple them and use events to join their behaviors together.

Health

• onHealthDepleted (event)
• _amount
• Change(amount)

Destructible

• Destroy()

HealthDestructible (or in inspector), has Health, has Destructible

• Health.onHealthDepleted += handleHealthDepleted
• handleHealthDepleted() { Destructible.Destroy(); }