The ideal activity description should include:

• A short description of the activity including possible modes of use and its fields of application.
• A description of all parameters (activity, input and output). This should include the name, type, required yes/no and details of precedence rules if the same parameter appears as an activity and an input parameter.

Note: Naming conventions should be observed here as in any other area of coding. Activity names and perhaps more importantly parameter names should be standardized and used consistently to avoid confusion and unnecessary debugging time.