Adding an acs_objects_description table is just and ad-hoc way to store meta-data about content, so If you have objects that need name and url descriptions, why not just store them in the CR and be done with it? What you seem to be proposing is to build an under-featured CR out of the acs_objects table. So now we'll have a CR that many people think is too compicated and over-featured, and to fix this problem, we will instead add CR like features to acs_objects and create a parallel lightweight CR repository in acs_objects.
It seems that it would be better to address shortcomings in the CR, rather than create shortcomings in acs_objects.
