Module table of contents are poorly formatted when long type hints are present

When a function has a very long call signature, potentially because it's making extensive use of type hints, the module table of contents generated by AutoAPI ends up being poorly formatted. The column with the function call signature in it becomes very wide, and the one-line docstring description gets squeezed off to the righthand side, potentially requiring scrolling to view.

See this module for example.

Possible solutions might be stripping type hints from the call signature in the table of contents, or using a multi-line format for the call signature including type hints.

Start by inspecting the generated module table of contents in the linked AutoAPI example and reproduce it with a function that has a long type-hinted signature. Trace the formatting responsible for the wide call-signature column; done means the one-line description remains visible without requiring horizontal scrolling, with coverage for the long-signature case.