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 |
|---|---|
| Include example usage directly in the description | Concrete input/output examples embedded in a tool's description reduce ambiguity far more efficiently than more prose -- showing the model one or two realistic calls (and, where useful, one call that should NOT be made) often resolves edge cases prose alone leaves open. |
Machine-readable version: GET /api/practices?category=examples