The language and UX aroundno-unsafe-call (and similar rules) messages indicate "anerror type typed value", which seems unclear and maybe also misleading.

Before You File a Bug Report Please Confirm You Have Done The Following...

• I have tried restarting my IDE and the issue persists.
• I have updated to the latest version of the packages.
• I havesearched for related issues and found none that matched my issue.
• I haveread the FAQ and my problem is not listed.

Playground Link

https://typescript-eslint.io/play/#ts=5.5.2&fileType=.js&code=MYewdgzgLgBApgGxgXhgegFQZgASgTwAc4YBvAUQTgFs4woBfGDNGAClIYEoAoHxAHQALAE5wAZgICWYYAgCuAEzgQ2AcgCGAI2BreQA&eslintrc=N4KABGBEBOCuA2BTAzpAXGUEKQAIBcBPABxQGNoBLY-AWhXkoDt8B6Jge1tieQEMAZolpk%2B8eOiiJo0DtEjgwAXxBKgA&tsconfig=&tokens=false

Repro Code

constel=/**@type {Element} */({})el.href.includes('abc')

ESLint Config

module.exports={parser:"@typescript-eslint/parser",rules:{"@typescript-eslint/<rule-name>":["error", ...<options>],},};

tsconfig

{"compilerOptions": {  }}

Expected Result

I expected the error message:

Unsafe call of a method on an `any` typed value

Differences:

• mentions the typeany (which is the only observable type in JSDoc withoutcheckJs: true)
• doesn't mention the typeerror
• less important: mentions "method"

Actual Result

I observed the error message:

Unsafe call of an `error` type typed value

Confusing parts:

• no mention ofany
• mentions the typeerror, which is unobservable in JSDoc withoutcheckJs: true
  • also, if I hear "anerror type typed value", then that could sound like something likeError, so even if this "error" language is kept in some form, maybe it should be disambiguated fromError
• less important: does not mention "method"

Using this in TypeScript or withcheckJs: true leads to a more understandable experience:

Hovering overhref inel.href shows that TypeScript is reporting an error:

Property 'href' does not exist on type 'Element'.

Additional Info

This also affects other rules, since they also create messages the same way.

The type for this seems to be coming from thets-api-utils functionisIntrinsicErrorType

• https://github.com/JoshuaKGoldberg/ts-api-utils/blob/2d6af536e6ecf9fae9a2db445dbe1db115955afa/src/types/typeGuards/intrinsic.ts#L92-L111

cc@JoshuaKGoldberg