A ProxyControllerRegistration is kind of a strange beast, as it represents a resource that has a dual nature, both as a leaf resource on the local process and as the root resource on the remote process. One place where this falls apart is with getOperationDescriptions, which does nothing locally, resulting in only ops on the remote side being described.

But a ProxyControllerRegistration can also have local ops; e.g. stop/kill/destroy ops on a /host=x/server=y resource. But because of this bug those ops can be invoked but they do not appear in things like read-operation-names output.

UPDATE: this is a poor description as the real goal is to get correct metadata via read-operation-names, read-operation-description, read-resource-description and doing that will require more than changing ProxyControllerRegistration. There would need to be OSHs for those ops at the proxy address that understand how to integrate the data from the two aspects of the resource.

UPDATE 2: Similar discussion may apply to attributes.