1 practice, live from D1
Practices
Prompt-engineering best practices specific to tool/function description writing, grouped by category unless filtered. For general prompting techniques (not tool-description-specific), see subagentprompts.com.
| practice | description |
|---|---|
| Give parameters descriptive, self-explanatory names | Parameter names are part of the model's only signal for what a field means -- prefer a clear, specific name (and a short description on the parameter itself, not just the top-level tool description) over a short but ambiguous one. |
Machine-readable version: GET /api/practices?category=naming