MOVO exposes 15 tools across setup, model configuration, search providers, and external tool management. Most tools have descriptions (13/15), but schema quality is inconsistent. 8 tools lack visible input schemas or have incomplete parameter definitions. Naming follows verb_noun convention (setup_*, fetch*, create*, update*, delete*) but lacks clarity in distinguishing similar operations (updateTool vs patchTool). Parameter descriptions exist but are often generic ('Tool ID', 'Tool configuration'). No output schemas documented. Error handling and recovery guidance absent. Security concerns: API keys exposed as parameters (setup_model_test, setup_search_test). Overall definition quality is below production baseline due to schema gaps and missing output documentation.

• Remove API keys and secrets from tool parameters. Implement server-side secret injection: store credentials in environment variables or a vault, and pass only a reference (e.g., 'provider_id') to the tool. Update setup_model_test and setup_search_test to accept a provider_id instead of apiKey.
• Document output schemas for all tools. For each tool, specify the response structure: field names, types, and what each field represents. Example: 'Returns {tools: [{id: string, name: string, type: enum, status: enum}], total: number}'.
• Add input schemas to tools lacking them (setup_status, setup_model_providers, setup_search_providers, fetchTools). Even if a tool takes no parameters, declare an empty schema: {type: 'object', properties: {}, required: []}.
• Consolidate updateTool and patchTool into a single update_tool with clear semantics. If partial updates are needed, document which fields are optional and which are required. Alternatively, rename patchTool to update_tool_partial with explicit documentation of the difference.
• Enrich parameter descriptions with format and constraint details. Replace 'Tool configuration' with 'Tool configuration object containing type-specific settings (e.g., for HTTP tools: {method, headers, timeout}; for MCP tools: {command, args})'. Replace 'Test input parameters' with 'Object with key-value pairs matching the tool's expected input schema'.