Token Saver Desktop is a Tauri desktop app with 20 tools, but exhibits critical definition gaps. Most tools lack parameter descriptions entirely (e.g., detect_integrations, scan_local_sessions, detect_strategy_runtimes have empty input schemas {}). Tool descriptions are present but generic (avg ~80 chars, well below the 194-char baseline). No output schemas are documented. Error handling is minimal, tools return Result<T, String> with no recovery guidance. The codebase shows Tauri command registration but no MCP protocol implementation visible.

• Add explicit JSON Schema input definitions for all 20 tools. Even tools with no parameters should declare Input: {} with a description. Tools with parameters (e.g., open_release_url, acknowledge_claude_hook_events) must include type, description, and constraints for each param.
• Document output schemas for all tools. Define the structure of IntegrationDetection, SessionFile, StrategyRuntimeDetection, UpdateCheckResult, and other return types so LLMs know what fields to expect.
• Expand tool descriptions from ~80 chars to 100-200 chars. Include WHAT the tool does, WHEN to use it, and any prerequisites. E.g., 'Detects installed AI agent tools by checking for their configuration directories in the user's home directory. Call this first to see which agents are available before enabling connectors.'
• Add parameter descriptions for all inputs. E.g., open_release_url's 'url' param should state: 'GitHub release URL to open (must start with https://github.com/SiruGao/token-saver/releases/ for security). Example: https://github.com/SiruGao/token-saver/releases/tag/v1.0.5'
• Implement MCP protocol transport (HTTP+SSE or Streamable HTTP) instead of relying on Tauri IPC. Register tools via MCP's tool registration mechanism with proper schemas, descriptions, and error handling. This enables remote agent access and compliance with the MCP spec.