Replace Vague Adjectives in Mistral Prompts

Mistral's official prompting guide explicitly instructs developers to avoid subjective and blurry words: replace quantitative adjectives like "too long", "too short", "many", "few" with objective measures, and replace blurry phrases like "things", "stuff", "write an interesting report", or "make it better" with exact specifications.

Avoid: "Write a short, interesting report about many database things and make it better." Mistral Best Practice: "Write a 300-word technical report analyzing the top 4 PostgreSQL connection-pooling bottlenecks, including exact p99 latency thresholds and PgBouncer configuration parameters."