Waterfall tries to address this by making the "what you thought" as rigid as possible, but not surprisingly I can give you exactly what you asked for and you will find it lacking. Agile says I'll give you "good enough" often enough for you to decide when you're done as early as possible, but tends to be difficult to time box. My .02 worth anyway...
I feel tools are often an excuse for poor PMs to be lazy. A PM is probably not going to be everyone's best friend -- your job is basically to facilitate decisions by executive leadership and make sure those decisions are executed on. You don't need a fancy tool for that; you need to communicate often with everyone (which often means bugging development managers for reports when they have better things to do.) Tools can help with this -- making the reports easier to generate/consume, but at the end of the day this can be integrated with whatever task assignment process the development group uses internally (be that tickets, or post-it notes, or smoke signals...)
As for agile vs. waterfall, you're right. It's tough to get corporate suits out of the "well when will it be ready?" mindset. The nice thing about agile though is that you repeat the process much more frequently, so you can actually start to improve that process and shorten your sprint times and do more actual work in less time. Executives like to see that, so early in a project it helps to focus on that as long as the product is making progress.