I can understand what you are getting at. However, a more real world example should clear this up slightly. Both the variable name and method name are not conveying meaning in the above example.

  val underperformingEmployee = selectLowestPerformingEmployee();

which can be reduced to

  selectLowestPerformingEmployee().terminateEmployment();

But there are already a lot of strange state management issues with this code style. I would expect something more like this in the wild

  terminateWorstEmployee(){
    var employee = hrService.lookupEmployeeByLowestPerformanceReview();
    employeeTerminationService.initiateTermination(employee.id);
  }

When things are named and abstracted properly, it should be very clear what is happening. var conventions won't save you here.

Assignment from method calls seems to be the most likely place where this could POSSIBLY cause confusion. Maybe we can compromise on variable assignment directly from constructors? That seems to be the clearest example where the extra text is purely noise. It also causes a lot of line wrapping which indirectly causes even more noise.