I think the code example needs to be a little larger than what you showed in your "Loose" class in order for you to start to see and understand how to minimize coupling. Others might have better examples, but this was the first (simplest) example that popped in to my head. I'll start with an implementation that has high coupling and then refactor it to encapsulate information and use dependency injection.
Imagine you have a mechanic. One of the things this mechanic does is checks tire pressure on car tires. We could try modeling that like this:
The above example is not loosely coupled: the Mechanic knows about Tire pressure, even though that's an attribute of Tire, which in turn belongs to Car; and there is no way that we could build a Car with different tires (e.g. with a different initial pressure or different low pressure threshold). This is bad primarily because if anything about the Tires changes, the Mechanic class (two levels removed from Tire!) may be impacted. However, if we did something like this, we could reduce the coupling:
In this example, you can see that the dependency that Car has on Tires has been injected; instead of creating its dependencies itself, Car is given its dependencies at construction time. This makes it very easy to create Cars with different types of Tires. It is an especially useful concept for writing testable software, but I won't go into that right now. It works extremely well with interfaces: you expect an interface at construction time and let the context determine what concrete type it should be. For example, say Tire was an interface and we had AllSeasonTire and WinterTire as concrete implementations. When the Car was assembled, perhaps we find that it is late Fall. We could then decide to build the Car with four WinterTires (if the customer paid for them) instead of AllSeasonTires.
Similarly, the coupling between the Mechanic and the Tires is gone. Now, the Mechanic only talks to the Car. If we change the Car and add additional components to it that need to be checked to ensure the Car is in working order, the Mechanic doesn't need to care (the class doesn't need to change). If we change the type of Tires we used to assemble the Car to have different minimum pressures, the Mechanic isn't affected.
Hope that helps.
Don't count your weasels before they've popped. And now for a mulberry bush related tiny ad: