Thoughts on requirements managment software

Most development organizations in my experience follow a pretty simplistic method for documenting requirements (e.g. Microsoft Word).  In my group we have attempted to go to an even simpler tool for our BRD type docs - the Confluence wiki.  Detailed test level requirements are distinct from the higher level BRD though.  What generates this pondering?  Today I attended a session presented by CTS and Blueprint.  Blueprint is a software vendor that provides a very robust software requirements tool.  The tool includes some level of prototyping, wow though at the level of requirements involved in using this tool.  

Our group here follows an agile approach to development which often does not allow time to generate the best requirements.  This definitely has caused us problems with increased defects and difficulty defining proper behavior for our global QA team.  Recently we have added requirements phases into our development life cycle, specifically the BRD and TAD pieces.  I think this is the first step to moving into more regimented requirement documentation guidelines - however we will require one of two things to pursue the level of requirements embraced by organizations such as Blueprint:

1. More staff for reqs writing
2. Reduced development and time to market requirments to allow small staff time to develop reqs docs

With current economic conditions, option 1 is unlikely.  Option 2 isn't particularly appealing either for an organization trying to drive new product development and new revenue streams...