Single tool 'sigmeta_scan' has a basic description (89 chars) and minimal schema. Input schema present but lacks parameter descriptions, only 'target' with type string and description. No output schema documented. No error handling guidance, no parameter constraints (e.g., path validation, file size limits), and no indication of what 'normalized catalog' means or what JSON structure is returned. Tool name lacks action verb clarity ('sigmeta_scan' is domain-specific jargon; 'scan_signals' or 'analyze_signals' would be clearer). Description does not explain WHEN to use this tool, what prerequisites exist, or what the return structure contains. Baseline: 100% of A+ tools have documented return types; this tool has none visible.

• Add explicit output schema: document that the tool returns {"tool": string, "findings": [{"id": string, "sev": string, "where": string}], "score": number}. Include field descriptions.
• Rename tool to 'scan_signals' or 'classify_signals' to start with a clear action verb and reduce ambiguity.
• Add parameter description for 'target': 'File path or directory to scan for signal metadata markers (TODO, FIXME, XXX). Must be readable by the server process.'
• Expand tool description to 150 - 250 chars: explain what 'signal metadata' means, what the scan detects, and when to call it. E.g., 'Scans files in a directory for signal metadata markers (TODO, FIXME, XXX) and returns a normalized list of findings with severity levels. Use this to audit code for incomplete or flagged signal definitions.'
• Add error handling: document that invalid paths return a clear error message (not a stack trace) and suggest alternatives if the path does not exist.