ainimate-mcp has basic tool definitions with schemas present, but suffers from inconsistent naming conventions, minimal descriptions, and missing parameter documentation. Tool names mix kebab-case (get-current-scene) and snake_case (get_current_project), violating naming consistency. Descriptions are generic and under 50 chars for most tools, providing insufficient context for LLM selection. Parameter descriptions exist but are sparse (e.g., 'Scene ID' vs actionable guidance). No output schemas documented. Error handling and recovery guidance absent. The create-animation tool has a complex nested schema but lacks clarity on frame interpolation behavior.

• Standardize all tool names to snake_case (get_current_project, get_current_scene, create_layer, create_shape, create_text, create_animation). Consistency enables reliable LLM invocation.
• Expand tool descriptions to 100-200 chars. Include WHAT the tool does, WHEN to use it, and any prerequisites. Example: 'Retrieves the currently active scene in the project. Call this first to get the scene_id needed for layer and shape operations.'
• Document output schemas for all tools. Specify returned fields, types, and which IDs are needed for chaining. Example: get_current_project should return {project_id, name, scenes: [{scene_id, name}]}.
• Add parameter descriptions for all enum values and constraints. Example: type parameter in create-layer should note 'Determines rendering order: background renders first, foreground last.'
• Add error handling guidance to write tools (create-layer, create-shape, create-text, create-animation). Example: 'If scene_id is invalid, call get_current_project to retrieve valid scene IDs. If layer_id is invalid, call get_current_scene to list available layers.'