All 7 tools have basic schemas and descriptions, but quality is inconsistent. Tool names lack action verbs (inspect, doctor, timeline are nouns/descriptors rather than verb_noun patterns). Descriptions are present but generic (10-50 chars, well below the 50-200 char LLM-optimized baseline). Parameter descriptions exist but are minimal. No output schemas documented. All tools are read-only, which is good for safety, but error handling and recovery guidance are absent. No tool annotations (readOnlyHint, etc.) despite all being read-only. Schemas are present but sparse, most parameters lack constraints, enums, or detailed format guidance.

• Rename tools to verb_noun pattern: 'inspect' → 'get_project_inspection', 'doctor' → 'run_project_diagnosis', 'timeline' → 'list_project_timeline', 'projectDiff' → 'get_project_diff', 'conformance' → 'get_conformance_report', 'securityAudit' → 'list_security_findings'.
• Expand descriptions to 80-150 chars. Example: 'inspect' → 'Retrieve a read-only structural analysis of the project, including file tree, dependencies, and module boundaries. Use this to understand project layout before running other diagnostics.'
• Document output schemas for each tool. Specify what fields are returned (e.g., timeline returns array of {timestamp, event, caseId}; conformance returns {status, violations, recommendations}).
• Add readOnlyHint: true to all tool definitions to signal safety to agents and enable optimizations.
• Add numeric constraints to parameters: timeline.limit (1-1000), memorySearch.maxItems (1-500), securityAudit.maxFindings (1-1000). Add pattern/minLength to query and projectId.