Y* Governance Framework exhibits severe definition quality gaps. Tool names lack clear action verbs (check_hook, scan_pending_enforcement_candidates are vague). Descriptions exist but are domain-jargon-heavy and lack LLM-optimized clarity (e.g., 'Scans governance charters and CIEU drift events to detect enforcement gaps using 6-criteria framework' assumes deep domain knowledge). Input schemas are partially visible but lack type definitions for complex objects (payload, policy, registry, contract are typed as 'object' with no nested schema). No output schemas documented. Error handling is absent, tools fail silently or return generic responses. Parameter descriptions are minimal. Only 2 of 8 tools have actionable, LLM-friendly descriptions.

• Add explicit output schemas for all 8 tools. Document return type, field names, types, and what each field means. Example: check_hook returns {action: 'allow'|'block', message?: string, reason?: string}.
• Expand input parameter schemas from bare 'object' to full nested definitions. For 'payload', define: {tool_name: string, tool_input: object, session_id: string, agent_id: string}. For 'policy', define required fields and their types.
• Rewrite descriptions for LLM clarity. Replace 'Scans governance charters and CIEU drift events to detect enforcement gaps using 6-criteria framework' with: 'Validates whether a tool invocation complies with governance policies. Returns allow/block decision with reason. Call before executing high-risk agent actions.'
• Add error handling guidance to each tool. Document: (1) what errors can occur, (2) whether they are retryable, (3) what the LLM should do next. Example: 'If policy file not found, return error: "AGENTS.md not found. Initialize governance with: ystar init"'.
• Rename tools to start with clear action verbs: check_hook → validate_tool_invocation, scan_pending_enforcement_candidates → detect_enforcement_gaps, apply_finance_pack → configure_finance_rules, apply_healthcare_pack → configure_healthcare_rules.