I enjoy this community, even though I am new to it. I appreciate the care and editorial vision that exists, so my opinion is shared as a constructive contribution to the conversation.
I don't think it would be the end of the world to keep the "policy" as-is, however I think it should be more clearly articulated in the FAQs just to avoid having this discussion over and over.
Currently when one of these questions is closed, the following message appears:
Questions on User Experience - Stack Exchange are expected to relate to user experience within the scope defined in the FAQ. Consider editing the question or leaving comments for improvement if you believe the question can be reworded to fit within the scope. Read more about closed questions here.
When you consult the FAQ, there is no mention of tools being out of scope. In fact, the language is written in such a way that it encourages "practical" questions related to "actual problems":
You should only ask practical, answerable questions based on actual problems that you face. Chatty, open-ended questions diminish the usefulness of our site and push other questions off the front page.
Your questions should be reasonably scoped. If you can imagine an entire book that answers your question, you’re asking too much.
If your motivation for asking the question is “I would like to participate in a discussion about ______”, then you should not be asking here. However, if your motivation is “I would like others to explain ______ to me”, then you are probably OK. (Discussions are of course welcome in our real time web chat.)
By that measure, a specific question about how to use a UX tool is entirely valid according to the stated policy.
In my case I wondered if it would be in scope or out of scope, and was leaning towards not asking the question until I read the FAQ. As it is written, it encouraged me to post my question. Which was downvoted and closed.
My own opinion is that we should allow tools to be discussed, as the mechanics by which we ply our trade is how UX manifests itself in the world. This is already well established and supported on ux.SE for MANY tools... that aren't software. A/B testing. Personas. Usability Testing. These are all tools that are the subject of questions asking about "using" the tool. Including how to use Axure to illustrate an interaction seems to be the same thing, it's just that it's an executable you run on a computer, not a process/procedure you run in the physical world.
The concern I seem to be picking up from most of the comments on this thread is that the current policy results in a clean environment. More signal, less noise. I totally get that, and I value that. There is a justifiable fear that the current community could become overrun like some other SE communities.
The difference I see is that there currently are not that many tool-related questions. Using the "ignore tags" feature will ensure that those who are not interested in reading about tools can filter those posts out, and those who are, can get some additional information. If it does get out of hand, there is nothing to stop us from changing the policy back to a strict ban.
There is a really good question that was originally downvoted, revised, upvoted, and answered that is an excellent example of how tool related questions can add value to the community.
Further, I think including some tool questions is an opportunity to further some of the goals outlined in the stack improvement drive--primarily increasing the number of questions and expanding our reach to draw in more users.
A great summation of what I think could be a definition of what tools questions are in and out of bounds:
@Chris Super User is for power users of desktop software. Asking them a wireframing/prototyping question and expecting a UX-relevant answer wouldn't get you very far. The UX community, however, generally deals with this exact problem and can therefore help the OP. It's less a question of "what's the objective right place" and more of a "which audience is right for this question" issue. In other words, this is a process question, not a software question.
When it comes down to it, some tools are so specific in their application to UX that the only way to get any kind of meaningful answer is to go where the people who can answer your question are.
Is there a tool for managing user stories?
Falls into the "shopping request" category and yet was highly voted, favorited, answered, and viewed over 1200 times. These types of questions can add value to the site and there is a demand/interest in them.
BTW not flogging a dead horse here, just adding to the answer to collect examples and context for future thought.