Ok, I'll give it a try.
The parentVMPath parameter expects the path to the VM from which you want to spawn the pool (obviously).
Such a path looks something like this: /MyDC/vm/MyVM
Where MyDC is the datacentername, the vm folder is the hidden folder that holds the VMs and Templates hierachy and finally the name of the VM itself.
If your master VM is deeper in the folder structure, just add the folders to the path.
Ex: /MyDC/vm/Folder1/Folder2/MyVM
The parentSnapshotPath is similar to the previous parameter, but obviously should point to the snapshot from which the pool should clone.
Alan has a nice function to retrieve the snapshotpath in Update and re-composure of View Pools.
The vmFolderPath is where the VMs that are created for the pool should be stored.
Again similar to the previous parameters, but now for the folder.
Ex: /MyDC/vm/PoolFolder
resourcePoolPath should point to a resourcepool.
Such a path will look something like this: /MyDC/host/MyCluster/Resources/MyResourcePool
Note that host and Resources are again hidden folders !
datastoreSpecs: this one is not the most obvious one.
It wants the full path to a datastore in a cluster as specified by a resource pool.
See the VVGetDatastorePath function presented in Determining Paths to vSphere Datastore Objects
The composer_ad_id wants the ID of the AD domain in which the composer is a member server.
You can get this through: Get-ComposerDomain | select composer_ad_id
As a side note, have a look at the PowerShell Integration with View 5.0 white paper. It's perhaps not intended for the latest View version,
but it explains some of the parameters a lot better than I could 