When pushing new artifacts via API or wchtools, Assets are automatically tagged by Watson, but Content does not yet support auto-tagging (would take multiple additional API calls). Discussed with Authoring team and there is no technical reason it couldn't /shouldn't be done, it just hasn't been requested as a priority item yet. Requesting it now, as I've been asked why tooling doesn't get auto-tagging of content like it does of assets, yet it's an API inconsistency, not tooling specific.