Two tools with minimal descriptions and incomplete schemas. search-code has a 54-char description (below baseline 194 chars); list-files has 44 chars. Both schemas lack required field documentation and parameter constraints. No error handling guidance, no output schema documentation, no pagination support despite list-files returning potentially large results. Tool names follow verb_noun pattern (positive), but parameter descriptions are sparse. No tool annotations (readOnlyHint present in metadata but not in schema). Schemas are visible and properly typed, but descriptions fall well below production baseline.

• Expand search-code description to ~150 chars: 'Search for code patterns, functions, or keywords in the repository. Returns matching files with line numbers and context. Use this to locate implementations, find usages, or explore the codebase structure.'
• Expand list-files description to ~150 chars: 'List files and directories in a repository path. Returns file names, types, and sizes. Supports pagination via limit and offset. Use this to explore directory structure before reading specific files.'
• Add pagination params to list-files: limit (1-100, default 20), offset (default 0), and return total_count and has_more in response.
• Document output schemas explicitly in tool descriptions or as separate schema blocks: search-code returns {matches: [{file: string, line: number, context: string}]}; list-files returns {files: [{name: string, type: 'file'|'dir', size: number}], total: number, has_more: boolean}.
• Add error handling guidance: 'If no matches found, try broader query terms or check repository is cloned. If permission denied, verify GITHUB_TOKEN has repo read access.'