SwayWM MCP has critical definition gaps. Descriptions are minimal (10-20 chars), below the 50-200 char baseline for LLM-optimized tools. The 'execute' tool accepts arbitrary sway commands with no validation, constraint documentation, or error recovery guidance. No output schemas are documented. Tool names lack action verbs (e.g., 'workspaces' instead of 'list_workspaces'). No parameter descriptions exist for the 'command' parameter beyond a generic string note. Error handling in 'execute' returns raw error text instead of actionable recovery steps.

• Rename tools to start with action verbs: 'list_workspaces', 'list_outputs', 'list_windows', 'list_inputs', 'get_focused_window', 'execute_sway_command'.
• Expand descriptions to 50-200 chars. Example: 'list_workspaces: Retrieve all Sway workspaces with their properties (name, layout, focused status). Use this to discover available workspaces before switching or querying specific ones.'
• Add output schema documentation for each tool. Example: 'Returns array of workspace objects with fields: name (string), layout (string), focused (boolean), num (integer).'
• For 'execute', document valid sway command syntax, provide examples, and add validation. Consider splitting into specific command tools (e.g., 'switch_workspace', 'move_window') instead of a generic execute.
• Replace raw error messages with actionable guidance. Example: 'Invalid sway command. Valid commands include: workspace, move, resize, focus. See sway(5) man page for syntax.'

Inferred effective spec: <=2025-11-25.

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