### Problem/Motivation External comparison feedback between Tools API and the emerging Drupal core CLI initiative confirms the module's metadata model is the shape core is being asked to adopt: 1. **Operation kind** (`ToolOperation`: explain/read/transform/trigger/ write) — straightforward for core CLI to model as an attribute. 2. **Destructive flag** — related but distinct from operation kind (a write is not necessarily destructive); equally easy to model. 3. **Typed outputs** — the most significant piece for AI use: structured, named, typed return values instead of a stdout string and exit code. This is the time-sensitive item to influence early, and Tools API's typed output definitions are the working prior art. 4. **Per-tool access checks** — needs comparison with core CLI's permission handling; possibly a non-issue. 5. **Static requirements** — surfaced before invocation rather than as runtime failure (see the companion issue wiring checkRequirements()). This issue tracks the alignment work so the module benefits from — and informs — the core effort rather than diverging from it. ### Proposed resolution - Keep the metadata model stable through RC1 (operation kind, destructive, requirements, typed outputs are all attribute-level and freeze with the API). - Contribute the typed-outputs design experience to the core CLI effort early (point 3 is the time-sensitive one; the module's TypedOutputs + FormattedExecutableResult design and its LLM-facing lessons are directly reusable). - When core CLI attributes land, add a mapping layer so tool metadata translates without loss (as done for MCP annotations). - Longer term: a Drupal CLI invoker exposing tools as core CLI commands, joining Drush/AI/MCP as the fourth consumer — the existing Drush commands are the template. ### API changes None in this issue; it coordinates and sequences. ### AI usage (if applicable) - [x] **AI Assisted Issue:** This issue was generated with AI assistance, but was reviewed and refined by the creator. - [x] **AI Assisted Code:** This code was mainly generated by a human, with AI autocompleting or parts AI generated, but under full human supervision. - [ ] **AI Generated Code:** This code was mainly generated by an AI with human guidance, and reviewed, tested, and refined by a human. - [ ] **Vibe Coded:** This code was generated by an AI and has only been functionally tested.