It should be a tool that's used by developers to help adopt tooling.
When adopting something new, or experimenting with a new tool, it is important to keep track of the experiences, good or bad, of using the tool and the consquences of it.
- Be API first - this is important so that it would be able to easily integrate with different tooling, not only for updating but also for querying, so that you could create different UIs for it (website, github/bitbucket, slack, etc)
- Have a social part - commenting, sharing, voting, etc. This is good for both engagement, and is a good source of context for when the evalutation is to be concluded.
- SUPER BONUS - GPT to extract summary of conclusion in a structured format, good for different documentation sites.
- Comparisons - for cases where multiple tools are used, you should be able to collect information about different tools, and perhaps how they relate to eachother.