Single tool with generally good schema definition and parameter descriptions, but description clarity could be improved. Tool has proper JSON Schema with typed parameters and constraints. However, the description lacks some LLM-optimization patterns (no explicit WHEN to use guidance, no dependency hints). Error handling in the source is basic (try/catch with success message but no recovery guidance for edge cases).

• Rewrite tool description to follow LLM-optimized pattern: 'Generate a map screenshot for visualizing geographic coordinates, routes, and points of interest. Call this when the user needs a visual representation of map data. Returns a PNG file saved to disk.' Include explicit WHEN to use.
• Add structured error handling with actionable recovery guidance: validate center coordinates are within [-90,90] lat and [-180,180] lon before calling puppeteer; catch and return clear errors like 'Invalid center latitude: must be between -90 and 90, got {value}'; validate outputPath is within allowed directory to prevent path traversal attacks.
• Document output schema explicitly: 'Returns {success: boolean, path: string, details: {center: [number, number], zoom: number, dimensions: string}}' so LLM knows what fields exist.
• Add parameter descriptions that include validation rules: 'center [lat, lon], latitude must be -90 to 90, longitude must be -180 to 180' and 'outputPath, file path where screenshot will be saved (must be within project directory, no path traversal)'.
• Add security description: 'outputPath is sanitized to prevent directory traversal. Only PNG format is supported. Marker count limited to prevent resource exhaustion.'
• Add dependency hint: 'If you don't have map coordinates, call a geocoding tool first to convert address/place name to [lat, lon].'
• Implement input validation: sanitize outputPath, validate coordinate ranges, validate array bounds before screenshot generation.