This discussion is related to the proposal in#8164, where adding a dedicated description field for dependency groups in pyproject.toml was suggested.

I wanted to ask whether introducing an additional metadata block per group is the preferred direction, or if it risks increasing verbosity in pyproject.toml, particularly for projects with multiple dependency groups.

As an alternative, would it make sense to avoid extending the configuration format and instead focus on improving CLI discoverability? For example:

• displaying existing dependency groups via a CLI flag (e.g.poetry show --groups), and

• optionally capturing group descriptions interactively during group creation and displaying them only in CLI output, without persisting them in pyproject.toml.

I’m interested in maintainer feedback on whether keeping group descriptions out of the configuration file aligns better with Poetry’s design goals, or if explicit TOML metadata is considered acceptable in this case.