how to express model behavior in documentation generation tools?

I'm researching documentation generation tools and currently looking into OpenAPI+Swagger. There are a few things I'm looking to be able to do relating to describing transport-agnostic model behavior:attribute-level permissions (modifying attribute A requires permission X)conditionals, e.g. attribute A is required if B is presentrequired/optionalalways expect a value?if optional, then when empty is it present or omitted from the object?if present while empty, what is the default value?In OpenAPI+Swagger (or any other documentation tools you know) is this possible? This seems more fine-grained than what I've commonly seen supported and not sure if my search is in vain

Submitted July 03, 2020 at 11:58PM by izzlesnizzit