Inconsistent "question mark" sign placement with optional parameters

[ArmoredPony]

let's say I have a function with two optional parameters

---@param foo? string
---@param bar string?
local function func(foo, bar) end

foo parameter has its ? after its name and bar after its type.
When I hover my mouse over the function name, the ? sign appears after names of the parameters

But when I hover it over a parameter name, this sign appears after type of the parameters

It doesn't matter where I put this sign in ---@param annotation: after name or after type.

Same with classes

---@class Cls
---@field foo string?
---@field bar? string
local cls = {}
cls.foo = nil
cls.bar = nil

Is this inconsistency by design? Does it mean something? If not, I'd prefer always seeing it at the same place. May be always after a type.
This issue is pretty minor but I still wanted to report about it. Screenshots are from VS Code.

[C3pa]

I am not sure that foo? works as intended since the first word in the annotation is the parameter name, while the second word is the type used in type checking.

[sumneko]

It is in designed.

1. It is after param name when hovering a function, or after field name when hovering a table.
2. It is after type when hovering a variable.

[ArmoredPony]

Okay then... Can I ask why is it implemented as such?