Photo-agent has 6 tools with basic schemas and descriptions, but significant gaps prevent higher scores. All tools have input schemas with type definitions and descriptions, meeting minimum requirements. However, descriptions are generic and lack LLM-optimized guidance on WHEN to use each tool or what distinguishes them. Parameter descriptions are minimal (e.g., 'Path to the photo file' repeated across tools). No output schemas are documented. Error handling is absent, tools provide no recovery guidance. Tool names follow verb_noun convention (get_, set_, create_, export_) but lack clarity on distinctions (e.g., create_develop_preset vs create_virtual_copy both create checkpoints but serve different workflows). No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite clear risk classifications in metadata.

• Add output schemas for all 6 tools. Document what fields are returned (e.g., get_photo_metadata returns {metadata: {...}, lastModified: ISO8601, ...}). This enables LLMs to chain tools and extract required data.
• Expand tool descriptions to 100-200 characters. Explain WHEN to use each tool: 'Create a checkpoint to save current edits as a named preset for reuse. Use this before major changes to preserve a recovery point.' vs 'Create a virtual copy to branch edits without affecting the master. Use this to explore alternative treatments.',
• Add tool annotations: set destructiveHint=true on set_develop_settings, create_develop_preset, export_photos, create_virtual_copy, reconcile_virtual_copy. Set readOnlyHint=true on get_photo_metadata. This signals to LLMs which tools are safe to retry.
• Enhance parameter descriptions with format and constraint details. E.g., 'photo_path: Absolute or relative path to RAW or JPEG file (e.g., /photos/sunset.NEF). Must exist and be readable.' and 'settings: Object with Lightroom develop keys (e.g., {exposure: 0.5, contrast: 10, saturation: -5}). See Lightroom API docs for valid keys.'
• Add error handling guidance in tool descriptions. E.g., 'If photo_path does not exist, returns error 404 with suggestion to check file path. Retryable: yes.' This helps LLMs recover from failures without manual intervention.