API Reference Strategy

Manual chapters provide narrative and recipes.

This separation between narrative guidance and parameter-complete references is intentional. The manual answers workflow and design questions, while shared tool docs provide exhaustive argument contracts. Keeping these concerns separate makes the manual easier to read without reducing technical precision.

Detailed tool-level parameter references remain in shared tool docs.

Reference Boundaries

  • This manual focuses on concepts, workflow patterns, and runnable examples.
  • Tool parameter completeness remains in shared tool documentation.
  • Facade-level usage details are emphasized in object workflow chapters.