Two tools with significant definition gaps. Tool 1 (describe_imagemagick_interface) has empty input schema and generic description. Tool 2 (crop_resize_blur_bg) has complete schema with proper types and descriptions, but lacks output schema documentation and error recovery guidance. No enum constraints on 'mode' parameter despite fixed valid values. Descriptions are present but lack LLM-optimized guidance on when/why to use each tool. No parameter validation hints or dependency documentation.

• Add enum constraint to 'mode' parameter: {type: 'string', enum: ['blur', 'cover', 'contain'], description: 'Resize mode...'}
• Document output schema in tool description: 'Returns {ok: true, output_path: string, mode: string} on success.'
• Enhance error messages with recovery hints: 'Input file not found at {path}. Ensure path is absolute and file is readable.' instead of raw error.
• Expand describe_imagemagick_interface description to explain its role: 'Returns server metadata and available image processing modes. Call this first to discover capabilities.'
• Add parameter constraints to description: 'width and height must be positive integers (1-10000 pixels). Blur radius must be 0-100.'
• Add numeric bounds to width/height/blur parameters in schema (minimum/maximum fields) to prevent LLM from passing absurd values.