tool-contract-sync

To audit tool implementations against skill definitions and JSON Schema manifests, run a gap analysis to identify missing artifacts and trigger generation for tools lacking skill MDs, manifests, or evals. This enforces consistency checks across all registered tools.

Tools in the ToolRegistry may be missing skill MDs or manifests due to a broken three-way sync between tool implementations, skill definitions, and tool manifests. A gap analysis detects these missing artifacts and provides steps to regenerate them.

To generate missing evals and JSON Schema manifests for registered tools, run the gap analysis to identify gaps and trigger artifact generation. This creates missing skill docs, manifests, and golden-trace evals to close the synchronization gaps.

The best way to validate consistency of tool names and parameters across manifests is to perform a three-way sync audit. This process validates descriptions and parameters across tool implementations, skill definitions, and manifests, producing a gap report for remediation.

Yes, a ToolRegistry is required because the gap analysis applies specifically when tools are registered there but missing corresponding skill MDs, JSON Schema manifests, or evals. The registry serves as the baseline for detecting synchronization gaps.

You should run a gap analysis for tool contract synchronization whenever tools are registered in the ToolRegistry but lack corresponding skill definitions, JSON Schema manifests, or evals, ensuring every registered tool has complete and consistent artifacts.