Two tools with reasonable naming and visible schemas, but descriptions lack depth for LLM decision-making, and schema documentation is incomplete. The 'find' tool has a generic one-liner description (63 chars) that does not clearly state WHAT it returns, WHEN to use it vs 'gs', or what the 'domain_filter' parameter controls. The 'gs' tool description is more detailed (189 chars) and properly explains the symbol inspection workflow. Both tools lack documented output schemas, critical for LLM chaining. Parameter descriptions exist but some are vague: 'domain_filter' description says 'Alternative parameter name for query filter' without explaining what values it accepts or what domains are supported. The 'view' enum is well-defined for 'gs', but 'find' has no such clarity. Error handling is not visible in the tool definitions. No indication of pagination support, result limits, or recovery guidance. The tools appear to be READ_ONLY (good for safety), but this is not surfaced via toolAnnotations (missing feature).

• Expand 'find' description to 100-150 chars: state that it searches the codebase by identifiers and returns file candidates with relevance ranking. Explain when to use 'find' (broad keyword search) vs 'gs' (deep symbol inspection of a known file).
• Document output schema for 'find': describe what fields are returned (e.g. file paths, match scores, line numbers, symbol names). This enables LLMs to extract the right data for follow-up 'gs' calls.
• Document output schema for 'gs': describe the structure of symbols, imports, importers, and callers sections. Include field types (line ranges, display names, etc.).
• Clarify 'domain_filter' parameter: either rename to 'language_filter' if that's what it means, or explain valid values (e.g. 'typescript', 'javascript', 'python'). Add to description: 'Restricts search to files matching this language or domain.'
• Add enum or constraint documentation for 'query' parameter: does it accept regex, glob patterns, or literal strings? Include format guidance in description.
• Add readOnlyHint: true to both tool definitions to signal they are safe to call multiple times without side effects.
• Add pagination guidance: if result sets can exceed 50 items, add 'limit' and 'offset' parameters to 'find'. Document the cap: 'Returns up to 20 files; use offset to navigate results.'
• Add error recovery guidance: document what happens if query is invalid, file not found, or symbol not found. Provide actionable next steps (e.g. 'If no matches found, try a broader query term.').