The current behavior of the header description field is confusing because it allows the addition of variables or parameters within descriptions, giving the impression that they are usable during execution. This inconsistency is problematic, as descriptions can be added throughout the collection, but they do not function as accessible variables or shared data points during request execution. If descriptions are intended to hold variables, they should be consistently accessible and viewable like any other variables used within Postman.
Like this:
For instance, if I use the same request across multiple collections and utilize a variable within the description field, I expect to see the variable’s data. This visibility is crucial for understanding the variable’s information, especially when descriptions are meant to provide clarity and consistency across different requests and collections.