We used this style because it's the standard across the ESLint ecosystem.
I don't know if we should break from the standard unless we think it really imported the UX? Maybe we just need to work on better / clearer /ore succinct descriptions?

Examples:
https://eslint.org/docs/rules/array-callback-return
https://github.com/jest-community/eslint-plugin-jest/blob/HEAD/docs/rules/consistent-test-it.md
https://github.com/import-js/eslint-plugin-import/blob/HEAD/docs/rules/no-unresolved.md
https://github.com/sindresorhus/eslint-plugin-unicorn/blob/main/docs/rules/better-regex.md

Oh that's very interesting. In general this is kind of a violation of what a heading is supposed to be, no? I don't know of any precedent for using the top level heading in a file to describe anything like this description. Is this exclusively in ESLint?

I think the idea is that the title is kind of just the tagline for the rule to help people figure out what it does at a glance to save them reading the entire page?

I'm not sure exactly! This convention came from people copying the ESLint core docs.

Moved to ESLint core: eslint/eslint#15471

Per eslint/eslint#15471 I think we can consider this accepting PRs! 🙌