GitNexus Fleet has 5 tools with basic schemas and descriptions, but significant quality gaps. All tools have descriptions (10-50 chars, below the 50-200 char baseline for LLM optimization), and input schemas are present but minimal. Parameters lack detailed descriptions explaining constraints, formats, or dependencies. No output schemas are documented. Error handling is absent, tools return raw results with no recovery guidance. The 'cypher' tool exposes a raw query interface, which is powerful but risky without input validation or error context. Tool names are reasonable (query, impact, context, list_repos) but descriptions are too terse to guide LLM selection effectively.

• Expand tool descriptions to 50-200 chars. Example: 'query' → 'Search code across indexed repositories using natural language. Returns matching symbols, files, and context. Use when you need to find where a function is defined or used.'
• Document output schemas for all tools. Specify fields (e.g., results: [{symbol, file, line, context}], total_count, next_cursor) so LLMs know what to extract.
• Add parameter descriptions with constraints. E.g., 'direction' → 'One of: upstream (callers), downstream (callees), or both. Upstream shows what calls this symbol; downstream shows what it calls.'
• Add input validation and error recovery guidance to 'cypher'. Validate Cypher syntax; return 'Invalid Cypher: <error>. Try: MATCH (n) RETURN n LIMIT 10' instead of raw parse errors.
• Implement pagination for tools returning lists (query, impact, context). Add limit and offset/cursor parameters; return total_count and next_cursor so LLMs can fetch large result sets incrementally.