You don't need the extra create_generated_clock command at the output. The rule is clock paths end at a flop. They will go through other things though.
When you do create_generated_clock and add it to the output of a flop, you create a new clock on that pin. So, when you enter those three create_generated_clock commands you will have three clocks, each coming out of one of the flops. They will all propagate though the muxes and other simple logic gates, so at trost you will see all three clocks. This is the default behavior. If you want to test this you can try report_timing -from [get_clocks clockname] to each one of the three clocks and you can see that the logic clocked by trost is being checked by each of the three clocks.
Usually that is all you need. (If you are using mux-based clock dividers,where the mux is used as a logic gate to mix two different signals and generate the clock, then you would need a create_generated_clock on the output of the mux and describe what the final clock you have. This is not your case though).
Now, the -add and -master_source... That is in case you need to make more clocks from trost. Let's say you have another divider which divides clk_trost by 2. Then you would have a problem as each of the three clocks at the divider would need to be divided. So you could create three clocks at the output pin of your trost divider (which I called trostdividerout). The -add and -master_clock pins are so you can specify which is the source of each one so that the final clock has the correct propagation delay, timing, etc.
- create_generated_clock -clock trost_2by2 -source outofflopby2 -add -master_clock clk_div2 trostdividerout
- create_generated_clock -clock trost_4by2 -source outofflopby4 -add -master_clock clk_div4 trostdividerout
- create_generated_clock -clock trost_8by2 -source outofflopby8 -add -master_clock clk_div8 trostdividerout
You could also do this if you have a more complicated clock generator that can generate multiple waveforms. Let's say you have a flop that sometimes generates a 50% duty cycle, sometimes does a 25%, sometimes does something else. In that case you might want to do the -add -master to describe each clock you are generating.
You could ask if you need all these internally generated clocks. Is the fastest one enough? Well, if you just have nice posedge logic, perhaps not, but if you have a lot of flops being used as clock dividers and you often mix the clocks, for example some logic runs on clk_div2, some on trost_4by2, some on clk_div4 and so on, then you could have some odd clock reconvergence cases. Therefore, it is then best to simply try to make the SDC file to express reality as close as you can.