For the most part, the CmdletBinding attribute won't do much for a workflow. Workflows emulate cmdlets in that they won't bind unknown parameters, so [CmdletBinding()]
doesn't change that aspect of parameter binding any.
You can specify the default parameter set with [CmdletBinding(DefaultParameterSetName='DefaultSet')]
, that may be useful.
Note that if you use the Parameter attribute, a function/workflow will implicitly use cmdlet binding. Workflows can't take advantage of everything you could use with the Parameter attribute, e.g. accepting values from the pipeline won't be useful because the workflow can't specify a process block. You can still specify parameter sets, positional arguments, and help messages which might be useful.