Would this be sufficient?

Some Jenkins features (like the REST API) are more difficult to use when this
option is enabled. Some features, especially in plugins not tested with this
option enabled, may not work at all. Some reverse proxies may filter the "crumb"
parameter, resulting in failures when trying to use certain actions.

That sounds okay to me.

Code changed in jenkins
User: Daniel Beck
Path:
core/src/main/resources/hudson/security/csrf/GlobalCrumbIssuerConfiguration/help-csrf.html
http://jenkins-ci.org/commit/jenkins/16509dc22c7129f64c6c2668779b71de819912cf
Log:
[FIXED JENKINS-15252] Explain problems with CSRF protection

Code changed in jenkins
User: Oleg Nenashev
Path:
core/src/main/resources/hudson/security/csrf/GlobalCrumbIssuerConfiguration/help-csrf.html
http://jenkins-ci.org/commit/jenkins/8e0b87c0ace41478dce790eceb18019d32371242
Log:
Merge pull request #1438 from daniel-beck/JENKINS-15252

[FIXED JENKINS-15252] Explain problems with CSRF protection

Compare: https://github.com/jenkinsci/jenkins/compare/6ee4d4a92757...8e0b87c0ace4

Integrated in jenkins_main_trunk #3779
[FIXED JENKINS-15252] Explain problems with CSRF protection (Revision 16509dc22c7129f64c6c2668779b71de819912cf)

Result = SUCCESS
daniel-beck : 16509dc22c7129f64c6c2668779b71de819912cf
Files :

• core/src/main/resources/hudson/security/csrf/GlobalCrumbIssuerConfiguration/help-csrf.html