This is good for small packages. Adding text for every step would be overwhelming in a large package such as is typical in my organization.
Other than MailFailure, the names in the package still would not make a lot of sense to an outside viewer. To make it easier to read, use user friendly names like "Destination Production Table" and "Import Source" rather than "dstProdTable" and "impSource".
The text "All failures come back to here" in this sample is incorrect. The MailFailure step will be triggered to run if, and only if, the impSource fails. Each individual step should have its own MailFailure step.
If you are going to use a Dynamic Properties Task, you should set up a precedent to ensure that it runs before the task that needs to have this property set. This is especially important as your task get larger. If you have several tasks running simultaneously, DTS may force your Dynamic Properties task to wait while it runs other tasks, and by the time it runs, it may be too late. Don't assume that it's going to run before the task that needs it does.
My blog: SQL Soldier
SQL Server Best Practices: SQL Server Best Practices
My book: Pro SQL Server 2008 Mirroring
Microsoft Certified Master: SQL Server, Data Platform MVP
Database Engineer at BlueMountain Capital Management