If your artifacts tend to be larger documents, where most of the content is in the body, including tables, images, etc., then you should use the name field as a short descriptor of the content.  You could ignore the name field, in which case a name will be generated based on the initial content of the artifact, but it's less likely to be as descriptive as a name you provide.  (This usage is most analogous to creating documents on your PC/laptop). 

If your requirements are shorter text-only statements (e.g., The system must be able to operate in xyz conditions), then you're better off NOT specifying a name, and only specifying the content (primary text).  This is the primary usage for modules, and is why name isn't shown by default in modules.  In this usage, the auto-generated name based on the contents is likely to be adequate. 

You could use the module usage pattern without actually using a module.  E.g., put your relatively short requirements into the content of the artifacts, let the system generate names based on that (you aren't required to specify a name even in this usage), and use folders to organize the requirements.  In that case, it would be useful to be able to remove the Name field and only use the primary text field.  But our expectation is that most people using this pattern will use modules, because it also gives you ordering, hierarchy, headings, etc.

Hope that helps.