How to avoid the God Object in DI (Facade Services vs Over-injection)?

A God Object acts as a central repository for everything, often resulting from wrapping dozens of dependencies into a single injected 'Context'.

While creating a Facade to reduce constructor parameters is good, a God Object is bad because it lacks cohesion. It violates the Interface Segregation Principle. A consumer should only be forced to depend on exactly what it uses. Split God objects into tightly focused, cohesive Aggregate Services.