Single tool 'natosymbol_scan' has a basic description (71 chars) but critically lacks parameter descriptions. The input schema defines 'target' as a string but provides no guidance on what constitutes valid input (SIDC code format, file path, etc.). No output schema is documented. The description mentions 'APP-6/MIL-STD-2525 symbol identification codes' but does not explain when to use this tool or what 'scan' means in context. No error handling guidance. Tool naming is acceptable (verb_noun form) but the overall definition falls well short of production quality.

• Add parameter description for 'target': 'File path or directory to scan for code review markers (TODO, FIXME, XXX). Recursively walks directory tree.'
• Document output schema: 'Returns JSON object with fields: tool (string), findings (array of {id, sev, where}), score (integer count of findings).'
• Expand tool description to clarify actual behavior: 'Scan source code files for common review markers (TODO, FIXME, XXX) and return findings with severity levels. Use this to identify incomplete or flagged code sections.'
• Add error handling guidance: 'If target path does not exist, returns empty findings. If file cannot be read, skips it and continues scanning.'
• Rename tool to 'code_review_scan' or 'scan_code_markers' to match actual functionality and avoid confusion with military SIDC validation.