Do not pass function context if at max depth

[martin-purplefish]

As it stands, the agent just stops when it hits the maximum depth - this way it'll be forced to synthesize a reply.

[changeset-bot]

🦋 Changeset detected

Latest commit: c2698f3

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
livekit-agents	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[martin-purplefish]

PTAL @longcw @davidzhao - I was running into the occasional "max function calls nested depth reached" - I think just not letting it make function calls at max depth is a better user experience? lmk what you think.

[longcw]

This makes sense to me. I also noticed that when the max depth reached the agent may stop answering even user speech to the agent again, it will reach the max depth quickly again.
But it's better to add a warning there. @davidzhao @theomonnom wdyt?

[davidzhao]

agreed.. it'd be good to log a warning so users are aware that tools are not being used here. we should prioritize not having the agent being stuck

[martin-purplefish]

good call - fixed

[davidzhao]

lgtm!