We have a use case where we want to minimize and reuse the number of origin pools in F5XC, but want to differentiate based on what route and LB is associated with the origin pool. Adding a Description field or labels to Routes would allow us to better organize and manage the route objects while keeping the origin pools simple.