Mache provides 11 code-analysis tools with basic descriptions and minimal input schemas. All tools are READ_ONLY and well-intentioned for repository exploration, but definitions lack depth. Descriptions average ~60 chars (well below the 194-char baseline for A+ tools). Input schemas are present but sparse, most accept only a single string parameter with minimal constraint documentation. No output schemas are documented, forcing LLMs to guess result structure. Parameter descriptions are generic ('Symbol name to find definition for') without format guidance, constraints, or dependency hints. Error handling is not visible in the definitions. Tool names follow verb_noun convention (positive), but lack the specificity needed to disambiguate similar operations (e.g., find_definition vs find_callers both search for symbols but return different result types).

• Document output schemas for all 11 tools. Specify what fields are returned (e.g., list_directory returns [{name, type, path, size}]), their types, and which fields enable chaining to other tools.
• Expand descriptions to 100 - 200 chars. For each tool, answer: What does it do? When should the LLM call it instead of a similar tool? What does it return? Example: 'find_definition locates where a symbol (function, class, variable) is declared in the codebase. Use this to understand a symbol's signature and implementation. Returns the file path, line number, and code snippet.'
• Add format and constraint guidance to parameter descriptions. E.g., 'symbol: The fully qualified symbol name (e.g., package.ClassName.methodName). If ambiguous, returns all matches.' or 'pattern: A regex pattern or literal string to search for. Supports * and ? wildcards.'
• Clarify tool distinctions in descriptions. Explain why find_definition, find_callers, and search are separate: find_definition returns where a symbol is declared; find_callers returns all call sites; search returns any text match.
• Add pagination and result-limit guidance. Document: 'Returns up to 50 results. Use offset/limit parameters to paginate. If more results exist, include a next_cursor or total_count field.' Implement limit parameters if not already present.