[layer8]

The practical use is that the user knows they will still have the opportunity to back out of the operation, and not commit to it by the first click. I don’t think “will need more input” is that useful as an information by itself.

[hunter2_]

At first I was going to say that the opportunity to back out and the need for more input are identical: if the dialog consists only of a button to proceed and a button to back out, the user needs to choose one of those as input, and eliminating that need for input means eliminating the opportunity to back out.

But now I'm thinking that a need and an opportunity are very distinct. For example, browsers used to present a Save dialog during a download: was there a need for input? No, accepting the default filename works, and based on that, they no longer offer the opportunity to choose a filename. Thus, "..." indicates the opportunity, even if there is no true need.

[layer8]

In addition, if you consider a "Print" dialog, it would be conceivable that it only provides a print preview, but no further inputs, and has only command buttons "Print" and "Cancel". In that case, I still think the menu item should be "Print…" with an ellipsis, despite the lack of further input.

Conversely, you might conceivably have a command that requires additional input, but where the dialog box taking the input doesn't offer the option to cancel the operation. In that case, I would consider an ellipsis misleading, even though a lack of ellipsis might be confusing as well if the command doesn't make sense without additional input.