Critical failure: Tool definitions are not visible in source code. The verify-plugin.mjs file references 7 tools by name only (get_initiative_pulse, get_operator_chronicle, get_agent_status, get_morning_brief, orgx_inspect, orgx_recommend, orgx_search) but contains no schema definitions, parameter descriptions, or output documentation. Tool registration appears to happen remotely via the HTTP endpoint (https://mcp.useorgx.com/mcp?profile=claude-directory), making static analysis impossible. Per hard scoring rules: if tool definitions are inferred rather than directly visible, cap per-tool scores at 50; if schemas are not visible, schema score must be 0; if descriptions are missing, description score must be 0. All 7 tools fail these gates.

• Publish tool schemas in the MCP server response or in a discoverable manifest file. Include full JSON Schema definitions with type, description, and enum constraints for every parameter.
• Add 50 - 200 character descriptions to every tool explaining WHAT it does, WHEN to use it, and what it returns. Example: 'get_initiative_pulse: Fetch the current status and health metrics of all active initiatives. Returns initiative_id, name, status (active|paused|completed), progress_percent, and last_updated timestamp.'
• Document output schemas for each tool. Specify field names, types, and whether results are paginated. Example: 'Returns: {initiatives: [{initiative_id, name, status, progress_percent, last_updated}], total_count, next_cursor}'.
• Rename ambiguous tools: 'orgx_inspect' → 'get_orgx_details' or 'describe_orgx_state'; 'orgx_recommend' → 'get_recommendations' or 'suggest_actions'; 'orgx_search' → 'search_orgx_resources' or 'search_initiatives'.
• Add parameter descriptions and constraints to every tool. For each parameter, specify type, required/optional, enum values (if applicable), and format. Example: 'initiative_id (string, required): The unique identifier of the initiative to inspect. Format: UUID v4.'