Adding dependency to class only because another [child] dependency needs it – Design Smell?-Collection of common programming errors

Yes it is a design smell, your types should take only the minimum dependencies they need. If they require a service which requires other dependencies, then those dependencies should be injected to the service, not the type that uses the service.

If you are using an IoC container, it will take care of these dependency chains for you. If you need to instantiate new instances of a type at runtime, then you should inject factory types.