25 tools with visible schemas and descriptions, but significant quality gaps across the board. Most descriptions are terse (10-50 chars), many parameters lack descriptions entirely, and complex nested objects (layers, regions, operations) have no schema detail. No output schemas documented. Error handling and recovery guidance absent. Tool naming is consistent (video_*) but many descriptions fail to explain WHEN to use the tool or what it returns. This server would require substantial rework before production use.

• Expand all tool descriptions to 50-200 characters. Include WHAT the tool does, WHEN to use it, and what it returns. E.g., 'Resizes a video to specified width/height. Maintains aspect ratio by default (fit=contain). Returns output path and new resolution. Use before concatenating videos of different sizes.'
• Add full property schemas to all nested objects. For video_add_text.layers, define: {type: 'array', items: {type: 'object', properties: {text: {type: 'string', description: '...'}, x: {type: 'number'}, y: {type: 'number'}, fontSize: {type: 'number'}, color: {type: 'string', pattern: '^#[0-9a-f]{6}$'}}, required: ['text', 'x', 'y']}}.
• Document output schemas for all tools. E.g., video_get_metadata returns {duration: number (seconds), fps: number, width: number, height: number, codec: string, bitrate: number}. This enables LLMs to chain tools correctly.
• Add parameter descriptions and constraints. E.g., video_resize: width (1-7680, pixels), height (1-4320, pixels), fit (enum: cover|contain|fill|inside|outside, default: contain). video_adjust: brightness (-100 to +100), contrast (-100 to +100).
• Add error handling guidance to descriptions. E.g., 'If input file not found, check path or call video_get_metadata first to verify file exists. If format unsupported, call video_convert first.'