sfx_search is a multi-operation mega-tool combining 6 distinct responsibilities (search, download, tag, list, describe, play) into one tool with an 'operation' enum. This violates the single-responsibility principle and forces LLMs to reason about which operation to invoke. Descriptions are present but verbose (500+ chars) and lack clarity on when to use each operation. Parameters are well-typed with enums and defaults, but the tool's complexity makes it error-prone. show_sfx_browser_card has minimal description (50 chars) and empty input schema, making it difficult for LLMs to understand its purpose and when to invoke it. No output schemas are documented for either tool.

• Split sfx_search into 6 separate tools: search_sounds (query, duration_max, tags, page), download_sound (sound_id, destination), tag_sound (sound_id, tag_name), list_cached_sounds (tag_filter), describe_sound (sound_id), play_sound (sound_path). Each tool has one clear responsibility.
• Expand show_sfx_browser_card description to 100-150 chars: 'Display all locally cached sound effects as rich in-chat cards. Shows sound names, duration, tags, and file paths. Useful for browsing your SFX library without leaving chat.'
• Document output schemas explicitly. For sfx_search: specify what fields 'data' contains for each operation (e.g., search returns {results: [{id, name, duration, tags}], total, page}). For show_sfx_browser_card: specify structured_content format.
• Add error handling guidance to descriptions. E.g., 'If sound not found, returns {success: false, message: "Sound ID 12345 not found. Try search_sounds() with query."}' This teaches LLMs how to recover.
• Add parameter constraints to descriptions. E.g., 'duration_max: Maximum sound duration in seconds (1-300, default 30)' instead of just 'Maximum sound duration in seconds.' This prevents LLMs from passing invalid values.

Inferred effective spec: 2025-06-18+.

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