Single tool 'run_sixmo_form' has a clear action verb and comprehensive schema with all parameters typed and described. However, the tool description (127 chars) is borderline short and lacks critical context about prerequisites, side effects, and error recovery. The schema is well-structured with nested objects and proper constraints (minLength, format), but output schema is not documented, LLMs cannot predict the response structure. Tool annotations are present (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) which is good, but the destructiveHint=false is questionable for a tool that uploads files and modifies external state. Error handling returns a structured result but lacks actionable recovery guidance.

• Document the complete output schema in the tool definition. Include field types, nested structure, and what each field means. Example: 'Returns {success: boolean, artifacts: {screenshots: string[], domSnapshots: string[]}, diagnostics: {visitedStates: string[], retries: number}, error?: {code: string, message: string}}'.
• Expand tool description to 150-250 chars. Add: prerequisites ('Requires valid sixmo.ru form URL and accessible file path'), side effects ('Uploads file and modifies form state, not reversible'), and error recovery ('On timeout, check network and file permissions, then retry').
• Correct destructiveHint to true. This tool modifies external state (file upload, form submission). Agents need to know this is a write operation with consequences.
• Enhance error responses with actionable guidance. Instead of generic 'MCP_TOOL_FAILED', categorize errors: 'file_not_found: Check file path exists and is readable' or 'form_timeout: Network issue or form unavailable, retry after 30s' or 'invalid_answers: Verify all required fields are non-empty strings'.
• Add validation for file path parameter. Reject paths with '..' or absolute paths outside a safe directory to prevent path traversal attacks. Return clear error: 'Invalid file path: must be relative and within project directory'.