frida-mcp exhibits critical deficiencies across naming, descriptions, parameter documentation, and schema completeness. Of 3 tools, all suffer from inadequate descriptions and missing parameter-level validation documentation. Tool names lack clarity about intent (config_set is vague; config_save and config_init are domain-specific but not self-documenting for LLMs unfamiliar with Frida). Parameters lack type constraints, enums, ranges, and many lack individual descriptions. No output schemas are documented. Error handling is absent from the visible code. The server provides no guidance to LLMs on parameter relationships (e.g., 'os' must be set before platform-specific features, per the description, but no enum constraint or validation logic visible). The codebase shows mature Frida server management logic (AndroidServerManager, port forwarding, device checks) but no corresponding LLM-ready interface design.

• Rename tools for clarity: config_set → set_frida_connection or configure_frida_server; config_save → persist_frida_config; config_init → initialize_frida_project. Include action verbs that LLMs recognize.
• Add enum constraints to config_set parameters: os=['Android', 'Windows'], save_to=['global', 'project']. Enums are machine-parseable and prevent hallucinated values.
• Document all parameter constraints: server_port (1 - 65535), server_path (absolute path, readable/writable as needed), adb_path (path to adb executable, required if os='Android'). Add format and range guidance to descriptions.
• Add missing parameter descriptions: new_project_config_path in config_init should clarify default location, whether relative paths are accepted, whether parent directories are created, and permission requirements.
• Document output schemas for all tools. Specify what fields are returned on success (e.g., config_set returns {status: 'ok', updated_fields: [...]} or a config object with applied changes). This enables LLMs to chain operations.
• Add error handling guidance to tool descriptions. Example for config_set: 'If os=Android and adb_path is invalid, returns error with device detection guidance. If save_to=project but no project config exists, run config_init first.'
• Add tool annotations. Mark config_set, config_save, config_init as destructiveHint=true (modify server configuration) and idempotentHint=false (config_set may have side effects if save_to is set). This guides LLM retry logic.