ContextSource MCP provides 6 well-structured tools for code relationship analysis with complete JSON Schema definitions and detailed descriptions in Korean. All tools have explicit input schemas with typed parameters, enums, and constraints (e.g., limit bounds 1-200, depth 0-5). Descriptions are substantive (100-300+ chars) and reference internal requirements (FR-Q2, ADR-0012). However, descriptions lack explicit guidance on WHEN to use each tool vs. alternatives, error recovery paths are minimal, and output schemas are not formally documented in the tool definitions themselves. Tool names follow verb_noun convention (search_, get_, build_) and are unambiguous. Parameter naming is consistent (id, limit, depth, direction). No security issues detected (read-only operations, no secrets exposed). Composition is sound, tools chain naturally (search_entities → get_entity → get_callers/get_callees → get_subgraph). Main gaps: no tool annotations (readOnlyHint present in metadata but not in schema), limited error guidance, and output structure not formally specified in tool definitions.

• Add formal output schema definitions to each tool (e.g., 'Returns: {entities: [{id: string, name: string, kind: EntityKind, filePath: string}], total: number, truncated: boolean}'). Document all response fields, types, and whether they are always present.
• Expose tool annotations in MCP schema: add 'readOnlyHint: true' and 'idempotentHint: true' to all tool definitions so LLMs know these tools are safe to retry and do not modify state.
• Translate all descriptions and parameter docs to English. Keep Korean as secondary if needed, but primary descriptions must be in English for cross-language LLM compatibility.
• Add error recovery guidance to descriptions: 'If entity not found, call search_entities(name=...) to discover the correct ID first.' Include examples of common error scenarios and next steps.
• Formalize parameter constraints in descriptions: 'id must match pattern p<projectId>/sym:<filePath>#<symbolName> (e.g., p1/sym:src/a.ts#Foo)'. Add regex patterns or format strings for complex parameters.