Critical gaps across all dimensions. Only 2 of 6 tools have visible input schemas (init, context); the other 4 (search, memory, session, entity) have NO documented schemas at all. Descriptions are present but minimal (10-50 chars), below the 194-char baseline. No parameter descriptions for most tools. No output schemas documented. No error handling guidance. Tool naming lacks clarity, 'session' and 'entity' are nouns, not action verbs. This server is not production-ready.

• Add input schemas to search, memory, session, and entity tools. At minimum, document required parameters (folder_path, session_id, query, etc.) with types and descriptions.
• Rename tools to action verbs: 'session' → 'manage_session' or 'get_session'; 'entity' → 'query_entity' or 'search_entities'. This helps LLMs infer intent from the name alone.
• Expand descriptions to 100-200 chars. Example: 'Search within project context to find files, symbols, or documentation. Returns matching items with file paths and line numbers. Use this to locate code before editing.'
• Document output schemas for all tools. Specify what fields are returned (e.g., search returns [{ path, line, snippet }]). Include IDs needed for chaining (folder_path, session_id, entity_id).
• Add error handling guidance. E.g., 'If session not found, call init() first. If search returns no results, try a broader query or check folder_path is correct.'