No need to define those in TCA. They can be created automatically (and @professorweb first patch already proves it), as long we can detect that a table needs those fields (l10n enabled or WS enabled).
The goal is to deduce the SQL scheme from the TCA, not duplicate it there.
Potentially incomplete list of TCA field config options that describe scheme information. Most of the are required for datahandler, some are only for display purpose:
MM, MM_insert_fields, MM_hasUidField, MM_match_fields, MM_opposite_field, MM_oppositeUsage, MM_table_where, file_field, foreign_default_sortby, foreign_field, foreign_label, foreign_match_fields, foreign_selector, foreign_sortby, foreign_table, foreign_table_field, foreign_unique, symmetric_field, symmetric_label, symmetric_sortby, dbType, exclusiveKeys, foreign_table_where, MM_table_where, allowNonIdValues, multiple, rootLevel.