LSP Add code action for adding labels to function arguments

[Norlock]

I would like to have a code action when I have the following:

pub fn link_text_tooltip_event(
  display_fields: List(String),
  linked_count: Int,
  map_global_msg: fn(global.Msg) -> msg,
) -> List(attribute.Attribute(msg)) {
  ...
}

The code action can now suggest to prepend the function args with labels:

pub fn link_text_tooltip_event(
  display_fields display_fields: List(String),
  linked_count linked_count: Int,
  map_global_msg map_global_msg: fn(global.Msg) -> msg,
) -> List(attribute.Attribute(msg)) {
  ...
}

[GearsDatapacks]

I don't think this is a good idea as it encourages using the internal parameter names as the public API.

[Kacaii]

I don't think this is a good idea as it encourages using the internal parameter names as the public API.

I usually add them when there are multiple arguments with the same type, to avoid passing values in the wrong order.

What should be taken in consideration when adding labels?

[lpil]

APIs should always be intentionally designed, the language server cannot think so it is unable to design suitable labels.