Single tool with adequate schema and annotations but significant gaps in parameter descriptions and output documentation. The tool name 'ableton_raw_command' is generic and does not follow verb_noun convention (should be 'invoke_ableton_command' or 'execute_ableton_command'). Tool description is 127 chars (within 10-1024 range) but lacks WHEN/WHY guidance. The 'params' parameter description mentions JSON-encoded strings but lacks format constraints or examples. No documented output schema beyond the code-visible return dict structure. Tool annotations present (destructiveHint=true, openWorldHint=true) but no idempotentHint clarity. Error handling not visible in provided code, no recovery guidance for invalid command types or parameter mismatches.

• Rename tool to 'invoke_ableton_command' or 'execute_ableton_command' to follow verb_noun convention and clarify intent.
• Add explicit output schema documentation: 'Returns {command: str, domain: str, stability: str, mcp_exposed: bool, result: any}. On error, result contains error details; check stability field to assess command maturity.'
• Enhance 'params' description: 'Parameter object for the command (dict or JSON string). If string, must be valid JSON. If parse fails, returns error with hint. See command_specs for per-command parameter requirements.'
• Add error recovery guidance: 'If command type is unknown, call list_ableton_commands() first. If params fail validation, the error message includes the constraint violated.'
• Document idempotentHint: clarify which commands are safe to retry (e.g., read-only queries) vs which have side effects (e.g., set_track_volume). Update annotation accordingly.