AfterEffectsServer has 9 tools with basic descriptions and schemas, but significant gaps in parameter documentation, error handling, and LLM-friendly design. Tool names are action-oriented (run-script, execute-script, inspect-comp, see-frame, analyze-audio-waveform, animate-to-audio, animate-from-data, render-comp, find-presets), which is good. However, most parameter descriptions are minimal (10-30 chars), and output schemas are not documented. No error recovery guidance, no permission gates for destructive operations (execute-script, render-comp, animate-* tools), and no input validation hints. The server exposes arbitrary ExtendScript execution without constraints, creating security risks. Parameter naming is inconsistent: some use full names (compName, audioPath, propertyPath), others are abbreviated (code). No enum constraints on mode parameters (animate-to-audio accepts 'waveform or peaks' as free text). Descriptions lack WHEN/WHY context for tool selection.

• Expand parameter descriptions to 50-150 chars and include WHEN/WHY context. E.g., 'Composition name (required). Use inspect-comp first to list available compositions in the project.'
• Add enum constraints to mode parameters: mode: enum('waveform', 'peaks') instead of free-form string.
• Document output schemas for all tools. E.g., inspect-comp returns {layers: [{name, type, duration, ...}], duration, frameRate, ...}. see-frame returns {frames: [{time, imageBase64, ...}]}.
• Gate execute-script behind a confirmation step or dry-run mode. Require explicit approval before executing arbitrary code. Log all executions with timestamp, code snippet, and result.
• Add error recovery guidance: 'If timeout occurs, check that After Effects is running and the MCP Bridge Auto panel is active. Retry after 5 seconds.' Include actionable next steps for each error class.