adapt wording

src/t2iapi/device/service.proto

@@ -224,8 +224,10 @@ service DeviceService {
         returns (InsertContainmentTreeEntryForSequenceIdResponse);
 
   /*
-  This manipulation is only applicable for devices which use static handles for descriptors across all MDIB
-  @SequenceID's.
+  This manipulation is only applicable for devices which use static handles for descriptors across all sequences of
+  MDIB's. If the device under test does not support static handles for descriptors, it shall return the GRPC Status Code
+  UNIMPLEMENTED. If the request contains a handle that is unknown for the device, it shall return GRPC Status Code
+  INVALID_ARGUMENT.
 
   Make available the BICEPS CONTAINMENT TREE ENTRY (as defined in IEEE Std 11073-10700-2022) that is represented by the
   provided handle in the device's MDIB. If the BICEPS CONTAINMENT TREE ENTRY is absent in the current MDIB, it shall be
@@ -239,8 +241,13 @@ service DeviceService {
 
   Example 2: Metric is already present in the current MDIB:
   - Metric with the handle "metric_1" is already present in the devices current MDIB
-  - InsertContainmentTreeEntryWithStaticHandle with handle metric_1 is executed
+  - InsertContainmentTreeEntryWithStaticHandle with handle "metric_1" is executed
   - no further action from the device is required
+
+   Example 3: the requested Channel is not known for the device:
+  - Channel with the handle "channel_a" is not present in the devices current MDIB
+  - InsertContainmentTreeEntryWithStaticHandle with handle "channel_a" is executed
+  - GRPC Status Code INVALID_ARGUMENT is returned since the requested Channel is unknown for the device
    */
   rpc InsertContainmentTreeEntryWithStaticHandle (BasicHandleRequest)
       returns (BasicResponse);