Single tool with minimal definition quality. upload_image has a basic description (89 chars, below 194-char baseline) and a single string parameter with minimal context. No output schema documented. No error handling guidance. No parameter constraints (e.g., file size limits, supported formats). No mention of prerequisites (CLOUDINARY_URL env var). Tool description lacks WHEN to use it and what happens on failure. Parameter description is generic and does not explain format expectations or constraints.

• Document output schema explicitly: 'Returns: {secure_url: string, public_id: string, width: int, height: int}' so LLM knows what fields to expect and can chain to downstream tools.
• Add parameter constraints to 'image': 'File path or HTTPS URL. Supported formats: JPEG, PNG, GIF, WebP. Max 100 MB. Local paths must be absolute.'
• Expand tool description to 150-200 chars: 'Uploads an image to Cloudinary CDN with auto-optimization. Requires CLOUDINARY_URL env var. Returns secure URL and metadata. Use when you need to host images for web delivery. Fails if file exceeds 100 MB or format unsupported.'
• Add error handling guidance: 'On failure, returns error with reason (e.g., "Invalid file format", "Credentials missing"). Retry with different format or check CLOUDINARY_URL is set.'
• Implement per-request credential scoping: accept optional cloudinary_api_key/api_secret as parameters (or via secure context) instead of relying on module-level env var. This enables multi-tenant use and better audit trails.