The "idea" here is, for any tool utilized in a macro project, to allow any configuration setting for that tool, if desired, to be exposed to the outside world, so that when the macro is utilized in a parent workflow, the embedded tool's configuration setting is directly available to the parent workflow.
A benefit here would be the ability for users to more easily build custom tools based on the existing tools: e.g. send all inputs and outputs through a validation phase of arbitrary complexity, while leaving the "integration layer" of the encapsulated tool untouched.