My commits just provide enough context for the commit. Some commit messages are long, some others are pretty short.
However, I try to stay away form commits like "bug fix" and then 500 additions and 324 deletions.
At my current company we use JIRA, so the commit message starts with the JIRA code, and usually the task itself has enough context for the commit message to be short and sweet.
If some of the changes made in the commit are unintuitive, I explain the motivation behind the changes.
Maybe in small codebases rollbacks are as frequent as they are in large codebases or teams of multiple people, so when longer commit messages are useful to understand what you're checking out/rolling back or removing.