Single tool 'code_intel' lacks critical definition elements. No input schema visible in source code, cannot verify parameter types, constraints, or structure. Description is present (67 chars) but generic and lacks actionable guidance on when/how to use the tool. No output schema documented. Tool appears to be a wrapper around an external Constellation service, but implementation details are opaque. Hooks inject contextual reminders but do not constitute tool definitions.

• Expose the full input schema for code_intel with explicit parameter definitions: query (string, required, description), scope (enum: 'definitions'|'references'|'impact'|'architecture', optional), limit (integer 1-100, default 20), offset (integer ≥0, default 0). Include descriptions for each.
• Expand tool description to 100-150 chars explaining: 'Search and navigate source code to find definitions, references, impact analysis, and architecture details. Use this before grep/rg for semantic code intelligence.' Add guidance: 'Call this first for code navigation; use grep/rg only for literal text search.'
• Document output schema: return array of results with fields: file_path (string), line_number (integer), snippet (string, max 200 chars), type (enum: 'definition'|'reference'|'usage'), confidence (0-1). Include total_count and next_offset for pagination.
• Rename tool from 'code_intel' to 'search_code_definitions' or 'find_code_references' to clarify the primary action and match verb_noun convention.
• Add error handling guidance: document what happens when query is empty, when no results match, when Constellation service is unavailable. Provide recovery steps (e.g., 'Try a shorter query' or 'Fall back to grep for literal search').