Single tool 'portfan_scan' has a basic description (73 chars) and minimal schema. Input parameter 'target' lacks a type declaration in the visible schema definition, only a description is present. No output schema is documented. The tool description does not explain when to use it, what prerequisites exist, or what the JSON structure contains. No error handling guidance. No parameter constraints (e.g., file path validation, directory existence checks). The implementation is simple but the definition falls well short of production quality.

• Add explicit 'type: string' to the 'target' parameter schema. Ensure the JSON Schema is complete with type, description, and any format/pattern constraints.
• Document the output schema: describe the JSON structure returned by portfan_scan (e.g., {findings: [{id, severity, where, ...}], score: number, tool: string}). Include field types and meanings.
• Expand tool description to 100-150 chars. Explain: 'Analyzes nmap XML output to identify and prioritize security findings. Accepts a file path or directory containing nmap XML files. Returns structured findings with severity levels and file locations.'
• Add constraint guidance to 'target' parameter: 'Path to a single nmap XML file or directory containing nmap XML files. Must be readable and contain valid nmap output.'
• Implement error handling that returns actionable messages: 'File not found at {path}' or 'Invalid nmap XML format: {reason}. Ensure the file was generated by nmap with XML output (-oX flag).'