Should I create a separate controller for actions that use multiple models?

Question

Design patterns

Ask for best practices from the toaster.
Sooner or later, I have actions in my controllers that use several models. I tolerate this for a long time, and then, if the actions grow, I move them to a separate controller. But something torments me, maybe it's better to leave everything as it is, so as not to fiddle with the standard rail structure of controllers once again? Or would it be better to make additional methods for the corresponding models and put the multi-model code there?
How do you act in such cases? What smart book says this?