The unusedparams analysis, like most gopls analyzers, uses the golang.org/x/tools/go/analysis framework for modular analysis, which is analogous to separate compilation in a compiler. That means that the analysis of a given package can access the package itself, and summaries of information obtained from the package's dependencies, but it cannot access information from packages that import the current package.

For the specific problem of unused parameters, that means it cannot report that a parameter of an exported function (such as your F) is unused, because another package could assign F to a variable of type func (int) (or a method to an interface of type interface{F(int)}), in which case applying the suggested fix to remove the parameter would break the program. The fix would be unsound.

Until recently, the unusedparams checker was disabled by default because it made exactly that unsound assumption, causing it to frequently give harmful advice. We recently rewrote it so that it is completely sound (no false positives), allowing us to enable it by default. Of course this means that may miss some true positives, but we believe that is the better trade-off.

So this is working as intended. You may find it helpful to periodically run a global analysis tool for detecting dead code, unused fields, unused parameters and so on, as such tools may have better precision; but gopls cannot run such analyses in real time.