@ebanster - I think that the QE, PO and Devs should come to an agreement on the minimum requirements to be specified in the stories. The minimum will depend on the thing you are testing. You could pick a story as an example and ask the QE why they need (in your opinion) test case like requirements for it. Involve other intelligent and experienced QEs/Devs in the discussion too. That way, they can explain why some of your QEs expectations are/are not justified.
From a QE perspective, I posted a related question in which I ask how much info should be put in a (API) story by the PO - Testing - What information should a story for an API contain?. Does this sound like the QE you are working with? I have stated the reasons why I want a little more details than most POs might provide. Do some or all of my expectations about the requirements seem reasonable to you?