Scored across 15 tools
The graph quartet (add_graph_node, connect_pins, set_pin_default_value, get_graph_nodes) has crisp read/write/link boundaries, and the discovery quartet (find_tools, describe_tool, call_tool, enable_toolset) is explicitly staged in each description. Minor overlap remains: set_properties and set_pin_default_value both write values (distinguished only by target: object property vs unconnected pin), and execute_python/call_tool can reach anything any other tool does, though both are framed as explicit escape hatches.
All 15 names are snake_case and 14 follow a verb_noun shape (add_graph_node, save_asset, get_object_info, enable_toolset). The single deviation is `undo`, a bare verb with no object, which is readable but breaks the otherwise uniform pattern.
15 core tools sits at the top of the ideal band and each one is load-bearing: graph authoring, property read/write, compile/save, discovery, dispatch, toolset expansion, and undo. The 1549-tool catalog is deliberately kept behind find_tools/call_tool rather than dumped into the list, which is the right scoping decision.
The core surface covers the full edit lifecycle for graphs and properties: read, create, wire, set values, compile, save, and undo, plus a Python escape hatch for anything unmodeled. The visible gaps (no actor spawn, level save, asset delete/duplicate, create_blueprint) are real but bridged by documented packs via enable_toolset and by call_tool, so they are workable rather than dead ends.