I often see agile stories that don't clearly describe what is being developed. Often, nothing is mentioned about how the story must be tested at a high level. I generally don't see this issue in UI stories because its obvious to see the changes from the screenshots.
So, it becomes hard or impossible for a QA to develop test cases for such stories right away. They have to chat with other people who are often busy and not available easily. Everyone wastes time in finding out information that should have already been in the ticket for the story.
How can one solve this problem ?
PS - I understand that some communication is required for daily work, but if people can start including basic information in stories, then work becomes easy & smooth.