Server has 10 tools with complete input schemas and descriptions visible in source. However, descriptions are minimal (10-80 chars, well below the 194-char baseline), lack actionable context for LLM selection, and parameter descriptions are absent. No output schemas documented. Error handling returns generic JSON objects without recovery guidance. Tool names are reasonable but descriptions do not explain WHEN to use each tool or dependencies between them (e.g., ptz_move vs ptz_abs_move distinction). No parameter descriptions for optional fields like 'speed' and 'seconds' defaults. Security: credentials loaded from config file (not visible in source), but no evidence of secret injection pattern. Composition is reasonable (single responsibility per tool), but no idempotency guarantees or batch operations.

• Expand tool descriptions to 100-200 chars. Include WHEN to use (e.g., 'Use ptz_move for relative motion; use ptz_abs_move for absolute positioning to a known angle'). Add dependency hints (e.g., 'Call ptz_get_position first to see current angle before ptz_abs_move').
• Add descriptions to all parameters. For 'speed' in ptz_move: 'Pan/tilt speed (1=slowest, 255=fastest)'. For 'codec' in play_audio: 'Audio codec (mulaw, alaw, pcm, etc.; defaults to mulaw)'.
• Document output schemas for each tool. E.g., camera_info returns {ok: bool, ip: string, channel_num: int, serial: string, device_type: int, model?: string, ...}. Include field types and whether fields are optional.
• Enhance error messages with recovery guidance. E.g., 'Camera offline. Check network connection and retry camera_status.' or 'Invalid preset index (got 99, max is 30). Call camera_info to see available presets.'
• Add tool annotations: mark camera_status, camera_info, ptz_get_position, capture, record_audio as readOnlyHint=true. Mark ptz_move, ptz_stop, ptz_abs_move, preset, play_audio as destructiveHint=true (or idempotentHint=true if safe to retry).