The language and UX around no-unsafe-call (and similar rules) messages indicate "an error 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 have searched for related issues and found none that matched my issue.
• I have read 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

const el = /** @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 type any (which is the only observable type in JSDoc without checkJs: true)
• doesn't mention the type error
• less important: mentions "method"

Actual Result

I observed the error message:

Unsafe call of an `error` type typed value

Confusing parts:

• no mention of any
• mentions the type error, which is unobservable in JSDoc without checkJs: true
  • also, if I hear "an error type typed value", then that could sound like something like Error, so even if this "error" language is kept in some form, maybe it should be disambiguated from Error
• less important: does not mention "method"

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

Hovering over href in el.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 the ts-api-utils function isIntrinsicErrorType

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

cc @JoshuaKGoldberg