Currently Mist generates the watched contract UI components based on the input ABI. As Solidity pretty much "randomizes" the order in which the ABI methods are generated, even if the original source had the call/transactive methods in some logical order, those will not be retained. As such, when adding a new contract to the watch list, if it has numerous constant methods, it will be very hard to find exactly the information looked for.

My suggestion would be to allow reordering the generated UI components (which could in the background move around the ABI methods between each other too). This would allow pasting arbitrary contract ABIs but still let the user sort them according to his own criteria and not have to rely on some random hasing order.