Describe the bug

A failure was identified in the multi-turn conversational context and agent routing logic when a required tool parameter is provided by the user in a separate message.

Steps to reproduce

Ensure the following agents and tools are active and configured:

• ATP_AGENT: Configured with a tool for sending Telegram notifications that requires a chat ID input parameter.
• ROOT_AGENT: The fallback agent that does not have the Telegram notification capability.

1. Start the Conversation (Agent asks for input).
2. Provide the Input (User provides the parameter).
3. Submit the Command (User continues the instruction).
4. Observe the Bug (System Loses Context).

Expected behavior

Investigate and fix (if required) a reported failure in the agent system where context is lost between turns, leading to an incorrect tool selection or a failure to use a provided input value (chat ID). The issue specifically manifests when a user provides an expected value (like a chat ID) in one message, but the agent system either fails to carry that context to the next turn or misinterprets the subsequent command, causing a different or less capable agent (ROOT_AGENT instead of ATP_AGENT) to take over. This may be related to how tool descriptions or input properties are defined in the Agent Development Kit (ADK).

ADK-TS Version

0.3.27

Environment

Node.js

Node.js Version (if applicable)

No response

Relevant log output

N/A

Additional context

N/A