Scored across 13 tools
Most tools target distinct objects: plugins (installed plugins), presets (a plugin's presets), params (automatable parameters), project_read (one file), and profile (many files) are clearly separated. The main risk is fl_call vs fl_exec, both of which run code inside FL, but the descriptions explicitly frame fl_call as a single API call and fl_exec as multi-call logic, which mostly resolves it.
There is a recognizable scheme — fl_* for live-link tools (fl_render, fl_install, fl_probe, fl_call, fl_exec, fl_transport) and project_* for file tools (project_read, project_write) — but the remaining tools are bare nouns (plugins, presets, params, profile, config) with no verb, so the set mixes prefixed-verb and plain-noun conventions. It stays readable and grouped, but not a single predictable pattern.
13 tools is well within the healthy 3-15 range and each tool earns its place, covering distinct concerns (plugin discovery, presets, params, project I/O, rendering, profiling, config, install/probe, live API, transport). Nothing appears redundant or filler.
The surface covers the domain broadly: plugin/preset/param discovery, project read/write with sound and effect references, render to audio, multi-project profiling, config, live-link setup, live API access, and transport control. A few conveniences (e.g., dedicated sample/loop browsing or mixer/track editing outside project_write) are absent, but the core create-read-render-play lifecycle is closed.