To enable tool reusability, what design principle is recommended?

• A. To enable tool reuse, design tools to be modular and well-documented with stable interfaces.
• B. To tailor tools to each task with bespoke interfaces.
• C. To frequently change interfaces without deprecation plans.
• D. To avoid documentation to save time.

Answer: (A)

Reusability comes from designing tools as modular components with stable interfaces and clear documentation. When a tool is modular, it has a well-defined role and can be combined with other tools without needing to know how each part works internally. Stable interfaces act as contracts: once you establish them, other code can rely on them across different tasks without forcing changes to the tool itself. Documentation is essential because it explains how to use the tool, what inputs and outputs to expect, and any configuration or constraints, making it easier to apply the tool in new contexts. Together, these practices let tools be swapped, extended, or composed in various workflows, which is what enables reusability. Options that tailor tools to a single task, frequently change interfaces without deprecation plans, or skip documentation hinder reuse by creating tight coupling, breaking changes, or a lack of guidance.