Two tools with minimal descriptions and incomplete schemas. darkroom_init has a 127-char description (acceptable) but only one required parameter with basic type. darkroom_optimize has a 156-char description but optional parameters lack type constraints and enums. Neither tool documents output schemas, error handling, or recovery paths. No parameter validation rules, no error categorization, no idempotency guarantees. Naming is verb-forward (good), but descriptions lack WHEN/WHY context and actionable guidance. Both tools perform file I/O with WRITE/READ_ONLY risk but no error recovery documentation.

• Add explicit output schema for darkroom_init: {success: boolean, configPath: string, cachePath: string, gitignoreUpdated: boolean, message: string}
• Add explicit output schema for darkroom_optimize: {processedCount: number, failedCount: number, results: [{file: string, variant: string, status: 'success'|'failed', error?: string}], availableVariants?: string[]}
• For darkroom_optimize, replace optional 'variant' string with enum: variant?: 'thumbnail' | 'hero' | ... (list all valid variants from config). Add description: 'Variant name to apply. If omitted, lists available images and variants.'
• Expand darkroom_init description: 'Creates shutterbox.config.ts with starter variants (thumbnail, hero) and breakpoints. Creates .shutterbox-cache/ directory. Appends to .gitignore if present. Fails if config already exists, delete it first to reinitialize.'
• Add error handling guidance: 'If projectDir does not exist or is not writable, returns error with actionable message. If .gitignore append fails, still succeeds but notes the failure in response.'