Single tool 'dockeraudit_scan' has a basic description (67 chars) and minimal input schema. The tool name lacks a clear action verb (scan is acceptable but generic). Input parameter 'target' has a description but no type constraints, format guidance, or examples. No output schema is documented, the tool returns JSON but the structure is not formally specified. No error handling guidance, no parameter validation rules, and no security considerations documented. The implementation is simple but the definition quality falls well below production standards.

• Add formal output schema: document that the tool returns {tool: string, findings: [{id: string, sev: string, where: string}], score: number}. Include field descriptions and example values.
• Enhance 'target' parameter description: 'Path to a Dockerfile or directory containing Dockerfiles. Accepts absolute or relative paths. Recursively scans subdirectories. Max depth: 10 levels.'
• Add error handling guidance to tool description: 'Returns empty findings if path does not exist or is not readable. Skips files that cannot be parsed. Returns error if path is outside allowed scan root.'
• Rename tool to 'audit_dockerfile_security' or 'scan_dockerfile_smells' to better convey intent and distinguish from generic scan tools.
• Document result limits: 'Returns up to 1000 findings. If limit exceeded, include a 'truncated' flag and guidance on filtering by severity or path pattern.'