Product Version = NetBeans IDE Dev (Build 201402100001)
Operating System = Windows 7 version 6.1 running on amd64
Java; VM; Vendor = 1.8.0
Runtime = Java HotSpot(TM) 64-Bit Server VM 25.0-b69

Consider:

public class Model {
	private final StringProperty description = new SimpleStringProperty();

	public Model() {}

	public String getDescription() { return description.get(); }
	public void setDescription(String desc) { description.set(desc); }
	public StringProperty descriptionProperty() { return description; }
	
}

Invoking autocomplete via CTRL-SPACE on an empty line in the Model class will pop up a list of suggestions including:

	public StringProperty getDescription() - generate

but the getter for the description property is already present and it is correctly returning String not StringProperty.  Worse is that accepting this suggestion and generating that method results in an error, since there are now two no-arg getDescription methods.   Autocomplete should be made aware of the JavaFX observable property pattern and autocomplete shouldn't insert code that conflicts with existing code.