People can write tool metadata and descriptions in Striker. Striker was designed to replace some of the more esoteric workflows around Toolforge accounts, but as a fun bonus it also doubles as a way to write tool descriptions for Hay's Directory. As such, when you are writing a description of your tool account and its function (and crucially, its default software license), you are also writing a description for a tool. This would be just fine if tool accounts on Toolforge lined up 1:1 with actual tools that they host. This is sometimes the case, but it is very common also to have one tool account for many tools, or for no tools at all because they're test/dev/sandbox accounts. (Multi-tool accounts do have the option for adding additional toolinfo files, but I am not sure it's very intuitive.)

I am interested in more explicitly uncoupling tool accounts from the tools they describe, from a data modeling point of view. A tool account would have a very small record (name, maintainers, license), and this record would have a 1:1 or 1:many relationship with tool catalog records. This will help us as we uncouple the general concept of tools from any particular hosting provider.