The nice way to build up a ResourceDefinition is with the Parameters object. And that works well with most add and remove handlers where the RD when building up the MRR generates a definition for the handlers.

But in cases where there needs to be some customization of the add description (e.g. deployment(-overlay) add where the content param can have fields that are not used in the content attribute) then the only option is in some way or other to override registerOperations. That or have the add OSH implement DescriptionProvider. Which we don't want.

Perhaps add setAddDescription/setRemoveDescription to Parameters, or

public interface SelfDescibingOperationStepHandler extends OperationStepHandler {
  OperationDefinition getDefinition();
}

Enhancing Parameters sound better.