The package descriptions for haskell-brainfuck witter on and on about
the virtues of the language the interpreter happens to be implemented
in, declaring it to be a "pure, lazy, functional language" and giving
a URL that readers can refer to for more information about it (as if
it was hard to guess).  This is all very well, but what they
completely forget to do is give readers any hint of the nature of the
language that the package actually provides an interpreter for.

Policy says "The description should describe the package (the program)
to a user (system administrator) who has never met it before so that
they have enough information to decide whether they want to install
it."  So technically you're breaking a "should", but I'll just call
this a wishlist bug as usual for package description reviews.

Meanwhile I've got three trivial "stylistic" nitpicks that I might as
well fix while I'm offering a patch:
 * you capitalise the name "Brainfuck" inconsistently;
 * the synopsis for hsbrainfuck also has an excess space;
 * the long descriptions shouldn't start by talking about an undefined
   "it" - if you're going to use boilerplate, phrase it so it works
   for all of them.

I would suggest the following text:

 Description: interpreter for the Brainfuck programming language
  Haskell-Brainfuck is an interpreter for the "Turing tarpit" programming
  language also known as Brainf*ck.