title: How do you avoid redundancy in documentation comments?
body: <p>We just started using StyleCop and the one thing I'm having a hard time with is the documentation requirements. I don't want to debate the usefulness of the tool, I'm just wondering if anyone has any guidelines or ways of thinking about documenting methods that makes the comments actually useful. I find that my comments often contain a lot of repetition just to satisfy StyleCop's requirements, like:</p>
  
  <pre><code>    /// &lt;summary&gt;
      /// Gets a dto of personal info.
      /// &lt;/summary&gt;
      /// &lt;param name="userId"&gt;
      /// The id of the user.
      /// &lt;/param&gt;
      /// &lt;returns&gt;
      /// A dto containing personal info.
      /// &lt;/returns&gt;
      public PersonalInfoDTO GetPersonalInfoDTO(int userId) {...}
  </code></pre>
  
  <p>Is there a standard way of phrasing a summary vs a returns description? What do you put in your param descriptions?</p>