Single tool 'boardroom_scan' has a basic description (67 chars) but critically lacks parameter descriptions. The input schema defines 'target' as a string with a description, but the tool itself provides no guidance on what constitutes a valid target path, expected format, or error cases. No output schema is documented, the tool returns JSON but the structure is not formally specified. No error handling guidance. The tool name lacks a clear action verb (scan is weak; 'analyze_metrics' or 'generate_report' would be stronger). Overall definition quality is below baseline for production tools.

• Add a detailed description to the 'target' parameter: 'Path to a directory or file to scan for metrics and code quality markers (TODO, FIXME, XXX comments). Must be readable by the process.'
• Document the output schema in the tool description: 'Returns a JSON object with fields: tool (string), findings (array of {id, sev, where}), score (integer count of findings).'
• Rename tool to 'analyze_code_metrics' or 'generate_investor_report' to clarify intent and match action-verb naming convention.
• Add error handling guidance: 'If target path is invalid or unreadable, the tool returns an error. Verify the path exists and is accessible, then retry.'
• Expand tool description to 150-200 chars explaining use case: 'Scans a codebase for TODO, FIXME, and XXX markers to generate a KPI summary for investor updates. Useful for assessing code health and technical debt before board meetings.'