A ModSecurity exception that doesn't disable the rule

CRS false positives are usually one rule firing on one field. The reflex is SecRuleRemoveById, which turns the rule off for the whole site and quietly widens your attack surface to fix a form.

Remove the target instead:

SecRuleUpdateTargetById 942100 "!ARGS:description"

Rule 942100 stays on everywhere else. It just stops inspecting that one argument.

Get the rule id and the offending target from the audit log rather than guessing. The Matched "Operator ..." line names both.