feat: added informative-docs rule

.README/README.md

@@ -601,6 +601,7 @@ selector).
 {"gitdown": "include", "file": "./rules/check-values.md"}
 {"gitdown": "include", "file": "./rules/empty-tags.md"}
 {"gitdown": "include", "file": "./rules/implements-on-classes.md"}
+{"gitdown": "include", "file": "./rules/informative-docs.md"}
 {"gitdown": "include", "file": "./rules/match-description.md"}
 {"gitdown": "include", "file": "./rules/match-name.md"}
 {"gitdown": "include", "file": "./rules/multiline-blocks.md"}

.README/rules/informative-docs.md

@@ -0,0 +1,61 @@
+### `informative-docs`
+
+Reports on JSDoc texts that serve only to restart their attached name.
+
+Devs sometimes write JSDoc descriptions that add no additional information just to fill out the doc:
+
+```js
+/** The user id. */
+let userId;
+```
+
+Those "uninformative" docs comments take up space without being helpful.
+This rule requires all docs comments contain at least one word not already in the code.
+
+#### Options
+
+#### `aliases`
+
+The `aliases` option allows indicating words as synonyms (aliases) of each other.
+
+For example, with `{ aliases: { emoji: ["smiley", "winkey"] } }`, the following comment would be considered uninformative:
+
+```js
+/** A smiley/winkey. */
+let emoji;
+```
+
+The default `aliases` option is:
+
+```json
+{
+  "a": ["an", "our"]
+}
+```
+
+#### `uselessWords`
+
+Words that are ignored when searching for one that adds meaning.
+
+For example, with `{ uselessWords: ["our"] }`, the following comment would be considered uninformative:
+
+```js
+/** Our text. */
+let text;
+```
+
+The default `uselessWords` option is:
+
+```json
+["a", "an", "i", "in", "of", "s", "the"]
+```
+
+|||
+|---|---|
+|Context|everywhere|
+|Tags|any|
+|Recommended|false|
+|Settings||
+|Options|`aliases`, `uselessWords`|
+
+<!-- assertions informativeDocs -->