Three tools with minimal descriptions (all under 100 chars) and no visible input parameter descriptions. Schemas are present but lack parameter-level documentation. Tool names follow verb_noun pattern (describe_*) but descriptions are generic and do not explain WHEN to use each variant or what distinguishes them. No output schema documentation visible. Error handling not evident in tool definitions.

• Expand each tool description to 80-150 chars. Example: 'describe_image_file: Analyze an image from a local file path using Claude Vision. Returns a detailed text description of the image content, objects, and context. Use when you have a file path available.'
• Add parameter descriptions: 'image_path: Absolute or relative file path to the image (PNG, JPEG, GIF, WebP supported)' and 'base64_image: Base64-encoded image data with optional data URI prefix (e.g., data:image/png;base64,...)'
• Document output schema explicitly in tool descriptions or a separate schema field. Example: 'Returns {"description": string, "confidence": number, "objects": [string]}'
• Add error guidance to descriptions: 'If file not found, returns error with available paths. If clipboard empty, suggests using describe_image_file or describe_base64_image instead.'
• Consider consolidating to a single 'describe_image' tool with a 'source' enum parameter (file|clipboard|base64) to reduce cognitive load and avoid tool selection ambiguity.

Inferred effective spec: <=2025-11-25.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry