This is feedback from @domaindrivendev:

    [HttpGet("addresses/validate")
    public bool ValidateAddress([FromQuery] Address address)

Today we'd describe address as a single parameter, despite the fact that it maps to different query string keys (address.zipcode, address.state, etc...). The feedback is that Swashbuckle (and other consumers) would always want this data to be broken down as much as possible (today it's as brief as possible).

We should either break this down fully (by property) or break down the first level (by property).

We'd of course apply cycle-breaking, and terminate on any type with a type-converter from string.