repo2graph exposes 4 tools with minimal schema documentation and sparse descriptions. Tool names are action-oriented (query, answer, build, export) but descriptions lack depth, none explain WHEN to use each tool, what prerequisites exist, or how they chain together. Input schemas are present but incomplete: 'query' and 'answer' accept only a string with no enum/format constraints; 'build' has empty input {}; 'export' lacks format enum despite mentioning 'e.g., json, html'. No output schemas are documented. Error handling is absent, no guidance on retryability, user-fixable vs fatal errors, or recovery paths. The 'build' tool is destructive (WRITE risk) but has no confirmation pattern or dry-run option. Parameter descriptions are minimal (1-2 sentences) and do not state ranges, constraints, or dependencies. No tool composition guidance, unclear how query→answer→export chain together or what IDs flow between them.

• Add output schemas to all tools. Document what fields query returns (e.g., result_ids, snippets, scores) so answer can reference them. Specify export output format (file path, content, size).
• Expand tool descriptions to 100 - 150 chars. For query: 'Search the code graph for symbols, functions, or patterns matching a question. Returns ranked results with file locations and context snippets. Use before answer() to ground responses.' For answer: 'Generate a grounded answer from query results, with citations. Requires prior query() call. Returns answer text + source references.'
• Add format enum to export: {"type": "string", "enum": ["json", "html", "markdown"], "description": "Export format. json: raw graph structure; html: interactive visualization; markdown: documentation."}
• Implement confirmation pattern for build: add optional 'confirm' boolean parameter (default false). When false, return dry-run summary (files to index, estimated size). When true, execute rebuild. Prevents accidental index wipes.
• Document error responses with recovery guidance. E.g., 'Query returned no results. Try: (1) broaden search terms, (2) call build() to refresh index, (3) check repository is indexed.' Categorize errors as retryable (network), user-fixable (bad query), or fatal (index corrupted).