Single tool 'sanitize_project' has a clear verb-noun name and basic description, but critical gaps undermine quality. Input schema is present with type and description for the 'path' parameter. However, the tool lacks output schema documentation, error handling guidance, and security considerations. The description (89 chars) is below the 194-char baseline and omits critical warnings about destructive behavior. No parameter validation constraints (e.g., path must be absolute, directory must exist). Error messages are generic ('Error: Path does not exist') without recovery guidance. The tool performs destructive file modifications (deletes dependencies, rewrites files) without dry-run support, confirmation steps, or audit logging, violating pattern:confirmation-request and pattern:audit-trail. STDIO transport caps overall score at 50; definition quality issues further reduce it.

• Add structured output schema: return {success: bool, purged_deps: int, scrubbed_files: int, errors: [{file, reason}], warnings: [string]}. Document in docstring.
• Implement dry-run mode (parameter: dry_run=true). Return what WOULD be deleted without modifying files. Require explicit confirmation for destructive operations.
• Expand description to 150-250 chars: 'Removes telemetry, tracking scripts, and marketing badges from a project directory. DESTRUCTIVE: modifies package.json and source files. Use dry_run=true first to preview changes. Requires absolute path to project root.'
• Add parameter constraints to 'path': 'Absolute path to project directory (must exist, must be readable/writable). Relative paths are rejected.'
• Enhance error messages with recovery guidance: 'Failed to parse package.json at {path}: {error}. Ensure file is valid JSON. Check file permissions.' Return per-file success/failure array instead of silent skips.