Writing API descriptions involves careful consideration of endpoints and their interactions, with the operationId playing a crucial yet often overlooked role in enhancing developer experience. An operationId is a unique identifier for each operation in an OpenAPI description, recommended to follow naming conventions for clarity and consistency across the API. Although not mandatory, using operationId thoughtfully can significantly improve API design by aiding in documentation navigation, code generation, and configuration of API gateways. The Redocly CLI suggests that operationId should be required, unique, and URL-safe, reflecting its importance. By adopting a consistent naming convention, such as a verb-noun pattern, and testing it for clarity, developers can make API endpoints more intuitive and reduce misconfiguration risks. Ultimately, the use of operationId can lead to smoother API integrations and a better overall developer experience.