It makes the OS snappier, not the disk
You seem to be assuming that the SSD controller always writes defragmented files in a sequential way which is not the case. Modern controllers keep track of empty flash cells and map 'disc sectors' as needed to empty cells. So an OS-level defrag will only make the disk faster if large regions of empty cells are available.
No, I realize that sectors are assigned to pages within blocks in a random fashion.
My reason for occasional defragging of an SSD is to eliminate overhead at the OS level. If a frequently read file is in 1000 fragments (as seen by the filesystem), then the OS has to issue 1000 separate SATA reads (and wait for the SATA read latency 1000 times). Each IO requires a couple of context switches to kernel mode, and processing at different interrupt levels.
If the file is contiguous (in the LBA sense), only one round trip over the SATA bus is needed. I'm reducing the latency and CPU time by defragging, not improving the speed of the disk itself.
The moment more than 50% of the drive has been written too, defrag will always have a negative effect as there won't be enough empty cells to write to.
That's where TRIM and over-provisioning are helpful. There's no magic threshold (like 50%), for the drive to support fast writing - it needs to have a buffer of "free" (erased) cells.
TRIM is helpful, because it tells the SSD which pages are unnecessary, so the drive does not have to copy these pages when garbage collecting - as well as helping to identify which cells are free (and can simply be erased) and which have few active pages.
Over-provisioning is also helpful, since that means that you can never actually "fill" the drive. Most drives have about 7% over-provisioning - your 256 GB (256,000,000,000 bytes) really has 256 GiB of space (274,877,906,944 bytes). That 19 GB is always available for the drive controller to use.
Some drives leave additional space free - like my 60 GB OCZ, which really 64 GiB of flash chips.
In some circumstances, the "best practice" is to provide additional over-provisioning by leaving part of the drive unpartitioned. With TRIM support, any free space in the partition is also effectively the same as over-provisioned.
This article has a pretty good description of how data is stored on an SSD: