Remove / Don't add a default "Description" field to Terms

Normally, when we think about a way to categorize content, the ontology is just loaded with terms--descriptions aren't necessarily always needed. Sometimes we use our taxonomies for purposes other than just categorization. While I realize we can certainly skip over the description field and not use it, I propose that core removes it entirely. Now that the Taxonomy terms can have fields associated with them, there are instances where a Summary+Full Description would be appropriate. Rather than have two separate fields to accommodate this functionality, why not just let the site admin apply the fields needed as required?

There are a few advantages to this approach:
1) We can lower the number of tables in the database required for fields. (A module doesn't always need to provide one off the bat).
2) Terms can function both as a categorization function and as highly functioning content.
3) We can re-use the field utilized for descriptions as required (not sure how EntityFieldController handles this if the field exists on another entity).
4) Modules which access taxonomy terms can enjoy lower database overhead (as far as I can tell) because the description field doesn't have to be loaded with the term anymore.

I would even go in-so-far as to say that this approach could be applied to other parts of the Drupal system. Because we can add fields at our whim, any other entities that want or use fields in the system can also adopt this approach.

I realize there's another issue that could be considered similar to this in the core queue that asks "Taxonomy should work more like nodes" (http://drupal.org/node/612056) but it appears to be dated (circa 2009).