Having a summary of name says it all
is not very helpful to anyone. Summaries always show up in search results, so they should be used to briefly describe what the build does. Are there specific skill combinations that make this build good at what it does? Is it a build designed for soloing a particular mob in a particular area? If a short description would be redundant for your build, leave it blank! Not having a summary is better than having a completely worthless one.
It is recommended that you explain the reasoning behind your build, especially why you chose one skill over another. If you don't, eventually, someone will come along and say, well why didn't you use this skill?
, even though you already ruled it out for one reason or another. If the build relies on a particular skill usage order or armor/weapon set-up to be effective, document it!
By default, any builds you create or builds belonging to the Official Builds category will be selectable to add to a team build. To have access to additional builds, they must be added to your favorites list.
Comments allow build authors to get feedback about their build. We encourage all commenters to provide respectful and useful feedback. Disagreements are natural, but rather than reduce the conversation to flaming or namecalling, use facts/examples/etc. to back-up your statements or suggest alternatives.
This feature is not complete yet.