XDCR Pause-Resume through CLI - does not work

Scenario
-------------
Basic unit test is failing - pausing/resuming XDCR through CLI does not work(screen-shot attached) .

[root@centos-64-x64 bin]# ./couchbase-cli xdcr-replicate -c 10.3.4.186:8091 --list -u Administrator -p
password
stream id: 398d509fe31fbabfe230a50121105630/default/default
status: running
source: default
target: /remoteClusters/398d509fe31fbabfe230a50121105630/buckets/default
[root@centos-64-x64 bin]# ./couchbase-cli xdcr-replicate -c 10.3.4.186:8091 --pause --xdcr-replicator=398d509fe31fbabfe230a50121105630/default/default -u Administrator -p password
SUCCESS: pause/resume replication
[root@centos-64-x64 bin]# ./couchbase-cli xdcr-replicate -c 10.3.4.186:8091 --pause --xdcr-replicator=398d509fe31fbabfe230a50121105630/default/default -u Administrator -p password
SUCCESS: pause/resume replication

Replication is not paused. When manually paused, CLI could not resume the replication either. I used -

[root@centos-64-x64 bin]# ./couchbase-cli xdcr-replicate -c 10.3.4.186:8091 --resume --xdcr-replicator=398d509fe31fbabfe230a50121105630/default/default -u Administrator -p password
SUCCESS: pause/resume replication

Note: The above commands were derived from usage.py.

Issues
---------
1. Basic Pause/resume functionality is failing. If the command is not right, no error message is thrown.
2. Success message is misleading when there's no effect on replication.
3. Format of message - SUCCESS: pause/resume replication ?
Messages should be more specific to the operation (pause/resume). If it is "pause", the message must read -
SUCCESS: paused replication from <src_bucket> to <dest_bkt> , similarly for resume.
4. Is there no better way to define the cryptic --xdcr-replicator param to make it user friendly? This can derived from REST given source and dest bucket name.