It goes further than that. The form gets passed the model and it's name and based on that also drivers the URL and http action to take.

IMO this is good coupling since it's very loose, trivially changed and eliminated boilerplate code that's just noise. Of course, as always, it depends on a number of circumstances what trade-off is best for you, your team, the specific problem, etc