Critical failures across all dimensions. No input schemas visible in source, all schema scores are 0. Descriptions are minimal (10-30 chars), failing the 20-char floor. No parameter documentation. No output schemas documented. Error handling absent. This server lacks the foundational definition quality required for production agent use.

• Add explicit input schemas to all tools with typed parameters (string, number, boolean, enum). Example: prepare_release should declare parameters like 'ontology_id' (string), 'version' (string), 'dry_run' (boolean).
• Expand all descriptions to 50-200 characters following LLM-optimized format: WHAT does it do, WHEN to use it, WHAT it returns. E.g., 'Prepare ontology for release by validating rules and materializing inferences. Returns validation report and materialization status. Call after run_release_gate succeeds.'
• Document output schemas for all tools. Specify returned fields, types, and pagination (if applicable). E.g., surface should return {ontology_id, version, rule_count, reasoner_type, capabilities: []}.
• Add confirmation/dry-run support to destructive tools. prepare_release and commit_materialization should accept a 'dry_run' boolean parameter and return what would change without applying it.
• Move tool definitions from test files to production code (HeadlessToolCatalog.java or a dedicated ToolRegistry class) with explicit registration, descriptions, and schemas visible in the main codebase.