Scored across 29 tools
Most tools target distinct resources or actions, but execution paths overlap heavily: ae_run_script, ae_call, ae_batch, and ae_tools can all invoke operations, while dedicated tools coexist with callable but unloaded tools. Descriptions clarify preferences, yet an agent must still decide between a direct tool, ae_call, or scripting for many tasks.
All tools use an ae_ snake_case prefix, mostly following verb_noun patterns such as get_, set_, add_, apply_, and render_. A handful are noun-only or bare verbs (ae_status, ae_batch, ae_checkpoint, ae_undo, ae_tools, ae_call), but the overall convention remains readable and predictable.
29 loaded tools is above the practical 3-15 range and exceeds the 25-tool threshold where selection cost becomes a concern. The AE domain is broad and meta-tools expose more unloaded tools, but the direct surface still feels over-scoped.
Core AE workflows are well covered: project/comp/layer inspection, property/keyframe/expression edits, effects, shapes, rendering, undo/checkpoint, and batching. Direct gaps remain for common operations like delete/remove, text editing, project save/open, align/select, and precompose, but most are reachable through ae_call or ae_run_script.