Koncepto provides 6 well-named, read-only tools with clear semantic intent (koncept_get, koncept_search, koncept_for_file, koncept_invariants_at_scope, koncept_affected, koncept_lint_naming). All tools have descriptions (10 - 100 chars, baseline 194 avg). Input schemas are present with type declarations. However, parameter descriptions are minimal or absent in most tools, output schemas are not documented in the source, and error handling guidance is not visible. Tool names follow verb_noun convention well. The server targets a specialized domain (concept graphs) with coherent composition, but lacks the depth of documentation and error recovery patterns expected for production-grade tools.

• Document output schemas for all 6 tools. Include field names, types, and descriptions. Example: koncept_get returns {id: string, name: string, description: string, tags: string[], participants: {file: string, role: string}[]}.
• Expand parameter descriptions to 50 - 100 chars each. For 'file' params, specify: 'File path relative to project root (e.g., src/main.ts). Glob patterns not supported.' For 'query', add: 'Search by concept name, description, tags, or glossary terms. Partial matches supported.'
• Add error handling guidance to tool descriptions. Example: 'Returns error if concept ID not found. Verify ID format (kebab-case) or call koncept_search to discover valid IDs.'
• Add limit and offset parameters to koncept_search and koncept_affected. Default limit=20, max=100. Document in descriptions: 'Results are paginated. Use limit and offset to retrieve large result sets.'
• Add a composition note to koncept_affected and koncept_lint_naming descriptions: 'Often used together: call koncept_affected first to identify impacted concepts, then koncept_lint_naming to flag naming violations in the same files.'