>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3595051. --> Reported by: [tim bozeman](https://www.drupal.org/user/2241356) >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>The AI tools shipped by <code>entity_blueprint_ai</code> and <code>entity_blueprint_config_ai</code> used verbose, module-prefixed function names such as <code>entity_blueprint_config_manage_plugin_collection</code>. These names are LLM-facing: they are the identifiers a model calls and the strings that appear in every tool schema and in inter-tool guidance text. The long names cost tokens, read inconsistently, and make cross-references in tool descriptions harder to scan.</p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>Move every tool <code>function_name</code> into a short, consistent <code>eb_</code> namespace (<code>eb_</code> for content tools, <code>eb_config_</code> for config tools), and update tool descriptions and the <code>EntityBlueprintToolBase</code> guidance message to reference the new names and the <code>eb_skill</code> / <code>eb_list_bundles</code> discovery workflow.</p> <table> <tr> <th>Old <code>function_name</code></th> <th>New <code>function_name</code></th> </tr> <tr> <td><code>entity_blueprint_add_element</code></td> <td><code>eb_add_element</code></td> </tr> <tr> <td><code>entity_blueprint_batch_operations</code></td> <td><code>eb_batch_operations</code></td> </tr> <tr> <td><code>entity_blueprint_create_entity</code></td> <td><code>eb_create_entity</code></td> </tr> <tr> <td><code>entity_blueprint_read_element</code></td> <td><code>eb_read_element</code></td> </tr> <tr> <td><code>entity_blueprint_read_entity</code></td> <td><code>eb_read_entity</code></td> </tr> <tr> <td><code>entity_blueprint_read_schema</code></td> <td><code>eb_read_schema</code></td> </tr> <tr> <td><code>entity_blueprint_remove_element</code></td> <td><code>eb_remove_element</code></td> </tr> <tr> <td><code>entity_blueprint_reorder_field</code></td> <td><code>eb_reorder_field</code></td> </tr> <tr> <td><code>entity_blueprint_restructure_layout</code></td> <td><code>eb_restructure_layout</code></td> </tr> <tr> <td><code>entity_blueprint_update_element</code></td> <td><code>eb_update_element</code></td> </tr> <tr> <td><code>entity_blueprint_validate_blueprint</code></td> <td><code>eb_validate</code></td> </tr> <tr> <td><code>entity_blueprint_config_create_config</code></td> <td><code>eb_config_create</code></td> </tr> <tr> <td><code>entity_blueprint_config_manage_plugin_collection</code></td> <td><code>eb_config_manage_plugins</code></td> </tr> <tr> <td><code>entity_blueprint_config_read_config</code></td> <td><code>eb_config_read</code></td> </tr> <tr> <td><code>entity_blueprint_config_read_config_schema</code></td> <td><code>eb_config_read_schema</code></td> </tr> </table> <p>Plugin IDs (the <code>id:</code> key, e.g. <code>entity_blueprint:create_entity</code>) are unchanged; only the LLM-facing <code>function_name</code> values change.</p> <h3 id="summary-api-changes">API changes</h3> <p>Backward-incompatible. The <code>function_name</code> is the identifier exposed to the model and the string by which <code>ai_agents.ai_agent.*</code> and <code>ai_assistant_api.ai_assistant.*</code> tool allow-lists reference these tools. Any agent/assistant configuration that enables these tools by name must be updated to the new <code>eb_</code> names, or the tools will no longer be available to that agent. The module is <code>lifecycle: experimental</code>, so the rename ships without a deprecation path.</p>