>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3526798. --> Reported by: [marcus_johansson](https://www.drupal.org/user/385947) Related to !134 >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>Currently the only way you can check the difference between a tool and an agent as a tool is to look for the custom_type definition in the Function Call plugin manager or to check if it extends a specific interface. Both thing can be performant and time consuming.</p> <p>Since the config agents will be the default way of doing agents in AI 2.0.0, we should already setup tool names that will be easily repriducable then. This means to store them similar to the id of the config agent.</p> <p>Unfortunately plugin systems doesn't allow dots, so we would go with colon. Just to make sure that it will not collide, we should use double colon.</p> <p>So the Agent Marcus Agent, that has the config name ai_agents.ai_agent.marcus_agent becomes ai_agents::ai_agent::marcus_agent.</p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>Set so the tools that exposes agents with id's will be named ai_agents::ai_agent::{config_name}.<br> Create an update script that updates the current agents that are using a subagent.</p>