We start with stereotypes and enrich them by filling out model details. My personal list of stereotypes, as well as your list, should be added to and adjusted over time. We distinguish whether an object serves a non-application specific purpose or if it models a concept that is specific to the problem domain. Utility objects are generally useful, non-application specific objects. Business or domain objects model some essential aspect of the problem domain.
Business objects have some correlation with concepts familiar to our software users.
Coordinators delegate tasks to others. They are a little less nosy form of controllers. Both are responsible for directing traffic. Traffic cops take a much more active role. They know why they are directing traffic and can adjust their behavior accordingly.