>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3556855. --> Reported by: [michaellander](https://www.drupal.org/user/636494) >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p><code>EntityFieldDefinitions</code> and <code>EntityBundleFieldDefinitions</code> have too much overlap. One was intended to be for describing field value schema, the other for field storage/settings schema, however they've become too similar which confuses AI. We improve their definitions and purpose to make the separation more obvious.</p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p><code>\Drupal\tool_content\Plugin\tool\Tool\EntityFieldDefinitions</code><br> Intended to be used for understanding field value schema and the definition as it pertains to setting this successfully. Consider renaming to <code>EntityFieldValueDefinitions</code>, also change from accepting an entity to accepting an <code>entity_type_id</code> and <code>bundle</code> vs an <code>entity</code> so that it can be used prior to entity creation. Remove anything focused toward storage/instance settings.</p> <p><code>\Drupal\tool_content\Plugin\tool\Tool\EntityFieldDefinitions</code><br> Intended to describe the field storage/instance settings for a field on a bundle. Should remove any reference to how to set field values using it.</p> <h3 id="summary-remaining-tasks">Remaining tasks</h3> <h3 id="summary-ui-changes">User interface changes</h3> <h3 id="summary-api-changes">API changes</h3> <h3 id="summary-data-model-changes">Data model changes</h3>