When reviewing a manuscript describing a new software tool, reviewers are often asked to assess its utility, quality, novelty, ...
I was wondering if, in addition to the classic comments on the manuscript, it was appropriate to make suggestion to improve the software functionality in itself (if the code is provided with the manuscript)?
This would be in the case of a software that is not good enough for publication (basically it does not do enough), and for which small additions will make it better. The comment on the code would therefore not be related to the coding "grammar" but ratter to improve the software tool usability for the final user.