Sure. I'm not trying to solve any particular problem, I'm just trying to learn what is possible and what isn't. I'm building something to interact with the API, and I'm trying to include local checks so the user can't even try to do things which the API simply doesn't allow. If tags on rules aren't a thing, then I simply won't let the user specify tags to set.
Also I was apparently reading some of the return values on NAT sections. They return a list of tags, but the documentation doesn't have a way to set the tags. Access sections and HTTPS sections also return a list of tags, but don't appear to have a way to set them (outside of 'set generic-object', anyway). The various rule types don't return a list of tags at all.
These little inconsistencies are driving me nuts. 😜 Most things have a comments field and a name field. Rule sections of any kind don't accept comments, but they have names. NAT rules don't have a name, but they have comments. This has led me to try to find all of the inconsistencies I can so I can handle them properly.