It's convenient, and probably fine when imports are unambiguous.

The problem here is that there were multiple possible imports for the same name, and in such situation, the extension picks an arbitrary one.

It feels rather like a bug (or a design issue) in the extension, that can be fixed, than a conceptual issue in automatic imports.