When defining functions, I prefer to limit the description to four key elements:
- The function’s purpose
- Its functionality
- Required params
- Expected outputs
This approach:
- Keeps function descriptions focused and specific
- Avoids including procedural instructions or inter-function dependencies
- Maintains clear separation between function definitions and broader system logic
I prefer handling procedural details and dependencies in the system message rather than in individual function descriptions.