Demiton

Each tool has a distinct role: ask_demiton reads, tell_demiton proposes writes/memory, exa_search queries the live web, forge builds roadmap items, instruct_demiton triggers platform agents, and switch_org changes tenant context. The main risk is mild overlap between instruct_demiton (investigate runs) and forge (build runs), and between ask_demiton and tell_demiton's memory_push, but the descriptions make the boundaries reasonably clear.

Three tools follow a clean verb_demiton pattern (ask_, tell_, instruct_) plus switch_org, all snake_case verb-first names. exa_search (vendor-prefixed) and forge (bare verb) are the deviations, but overall the set is readable and mostly predictable.

Six tools is well-scoped for a platform whose vast domain is intentionally collapsed into a single read tool (ask_demiton) rather than one tool per shelf. Each tool earns its place by covering a distinct capability: read, write, web, agents, build, and tenant switching.

The surface covers the full loop: reads (ask_demiton), proposed writes and memory pushes (tell_demiton), live web (exa_search), agent runs (instruct_demiton), builds (forge), and org context (switch_org). External write action_types are currently limited to a few timesheet/leave operations, but this is acknowledged as an evolving, admin-gated capability rather than a hard gap.