ctx++ defines 2 tools with reasonable descriptions and basic input schemas. Both tools have descriptive names (ctxpp_index, ctxpp_search) that start with action verbs and clearly indicate their function. Descriptions are present and moderately detailed (168-217 chars, within the 10-1024 char baseline). However, schemas lack completeness: parameters have types and minimal descriptions, but lack critical constraints (enums for 'mode', range/limit specifications for 'limit', format specifications for 'path'). Output schemas are completely undocumented, the LLM has no visibility into what fields to expect from results, breaking the pattern:tool-chain assumption. Error handling is not visible in the provided code. The tools themselves are well-scoped (index vs search), but parameter descriptions are sparse (12-28 chars each), falling below the 72-char baseline for production tools. The 'force' parameter lacks explanation of when/why to use it.

• Document output schemas for both tools. For ctxpp_index: return {indexed_files: int, skipped_files: int, symbols_indexed: int, duration: string, index_path: string}. For ctxpp_search: return {results: [{symbol_name: string, file: string, line: int, kind: string, relevance_score: float}], total: int}. This enables downstream tool chaining.
• Expand parameter descriptions to 50-150 chars each. Example for 'force': 'Force reindexing of all files, even if unchanged. Use after parser updates to refresh symbol extraction. Default: false (skip unchanged files).'
• Add enum documentation for 'mode': 'Search mode: keyword (fast, identifier-based), semantic (slower, concept-based via embeddings), hybrid (balanced, keyword + semantic with reranking). Default: hybrid.'
• Add constraints to 'limit': 'Maximum results (1-100, default: 10). Larger limits are slower and may exhaust context.'
• Add error handling guidance to tool descriptions. Example: 'If index fails, check that path is readable and .ctxpp/ is writable. If search returns no results with semantic mode, the index may lack embeddings, ensure embedding backend is configured (Ollama/OpenAI/Bedrock).'
• Document 'path' default behavior in schema. Either make path required, or state in description: 'Defaults to $CTXPP_PROJECT env var, or current working directory if unset.'
• Add per-parameter 'required' field to schemas explicitly. Currently only 'path' and 'force' visibility in ctxpp_index; only 'query' is clearly required in ctxpp_search.