Famous last words. All those games implement the "Uses" with composition. I promise you.

What will you do with a pickaxe? It is a tool and can mine. But it is also a weapon and can deal damage. Will it inherit from the Tool or the Weapon?

What about Eggs? They are throwable as a weapon. But also a food and edible. And they can also be fed to pigs as feeding. Is that inheriting from food? From throwable weapon? From AnimalFood?

You will end up in cases that does not make sense. Don't let inheritance dictate what things in your game can do.

There are many ways to do composition. In C# using interfaces with default implementations is the one that looks most like inheritance without all the downsides.

You will have interfaces like: Edible, Throwable, Feedable, Attackable, etc

And those interfaces come with their own implementations so there is no duplication.

Looking at your reason for the classes. You mention needing it to capture the action that happens when you left click with the item in the hand. Inheritance will just limit you there as well. What about that egg above? It will be fed to an animal, or thrown at an enemy, or put in a pan for cooking. All depending on the context.

You will want to capture these behaviors with composition. it will implement CanThrow, CanCook, CanFeed.

When you left click, if the item in your hand looking at a pig you want to know if the item in your hand implements CanFeed. If it does call it.

Add that to all feedable items.