Disagree! I have a goal to do laundry once a week. I think of it as my laundry goal. The title, or slug, is “laundry.” That’s a title - a short term that refers to the goal. It’s a handle or label for the goal. It’s the goal’s name.
This goal currently has no description, but if I were to put in a description, it might be “Do at least one load of laundry at least once a week.” That’s a description - a more lengthy explanation of what the goal actually requires, which goes into more detail. That’s clearly not a name.
If beeminder automatically named a goal after the description, it would be something like do_at_least7 which isn’t helpful.
So most of my goals don’t have a description. They don’t need one, because the name, which is the title and the slug, is sufficient.
Another example: I have goals to meditate in the morning, afternoon, evening, and night. They’re called amsit, aftsit, evesit, and nightsit. Those are the goal names. That’s how I think of the goals.
The descriptions are things like “>6 min 12-4pm” and those are just there to remind me of the requirements. It starts with a greater-than sign, so it wouldn’t work as a slug, and if beeminder automatically turned them into goal names, they’d be 6_min, 6_min2, 6_min3, and 6_min4.
So no, descriptions are not human-understandable titles - they’re additional explanatory notes that often only make sense with reference to the titles.
For instance, suppose you had goals for pushups and situps. In each case the description might be the same: “do 1 set of 15.”
Why? Because when you create a goal, you first think of what you want the goal to be. Say, to do pushups. Then, you give it a name based on that, like “pushups.” Then, you go into the description, where you flesh out how the goal works: “I want to do 1 set of 15.”
So the descriptions, which just enlarge on and expand the goal names, are not themselves helpful. Just the descriptions, “1 set of 15,” can’t even tell you whether you should do pushups or situps!