title: Generating end-point descriptions in Servant
body: <p>Servant <a href="http://haskell-servant.readthedocs.io/en/stable/tutorial/Docs.html" rel="nofollow noreferrer">provides a way</a> to generate documentation from the API definition. However, I see no way of (informally) documenting the functionality of each end-point. For the example used in the link above, the generated documentation contains:</p>
  
  <pre><code>## Welcome
  
  This is our super webservice's API.
  
  Enjoy!
  
  ## GET /hello
  
  #### GET Parameters:
  
  - name
       - **Values**: *Alp, John Doe, ...*
       - **Description**: Name of the person to say hello to.
  
  
  #### Response:
  </code></pre>
  
  <p>In the example above, what I miss is a way of documenting what the <code>GET /hello</code> end-point does, this is, I would like to have a way to augmenting the API docs with an informal description of each end-point.</p>
  
  <pre><code>## Welcome
  
  This is our super webservice's API.
  
  Enjoy!
  
  ## GET /hello
  
  Send a hello message to the given user. /&lt;-- My description.../
  
  #### GET Parameters:
  
  - name
       - **Values**: *Alp, John Doe, ...*
       - **Description**: Name of the person to say hello to.
  
  
  #### Response:
  </code></pre>
  
  <p>My guess is that this will require tagging the different end-points to identify them uniquely, something that as far as I know Servant does not support. However, I'm wondering how to solve this problem with what is available as of now.</p>