The part of the script that required editing was the sys.argv tool which always returns string objects as the arcpy.GetParameterAsText() code does. The sys.argv expressions have character limits and parameters will be cut short in cases of excessive text. Finally, the sys.argv expressions start with  instead of  which is used to get the filepath of the script itself. The advantages of embedding/importing a script into a script tool in terms of sharing the tool is that the only file required to share is the toolbox. From there, in terms of security, it can be password protected so that no one may edit or see the script without the proper password. To make Python scripts, and other file types, visible in ArcCatalog simply go to the customize menu and select ArcCatalog options. From there choose the file types tab and click “new type”. In the following dialog box you may import from a registry or enter the file type manually by entering the file extension and description. The file type will then appear in ArcCatalog.
The most useful part about using Python with ArcGIS is the ability to “test” out code in one environment before putting it to use in the other. I enjoyed this module most for #1. Everything actually worked right for me and #2. It was helpful use the toolbox, script and tool – editing in PythonWin and executing in ArcMap for a visible result. I found it most interesting the scope of edits that can be made in PythonWin in order to obtain the result desired in ArcMap. I also liked the ability to customize tools to obtain the desired results. I know I am not going to spend my life doing this (the world isn't ready) but I am happy to have the knowledge this course has given me.