Pgbouncer

Now as a DBA, to improve performance say idle connecting handling or anything, if I want to recommend pgbouncer to the team, what's the compelling reason would it be?

I may ask them to handle connections from application end and they may say ok but we still.may see idle connections are not closed.

So, at point and for what compelling reason I should tell my manager, we must go-ahead and use etc.

We use pg17 and in postgres itself I know idle_session_timeount,  transaction_timeout, statement_timeout. Is this enough? Will it abruptly kill queries and if so, isn't it bad?