Skip to content

Instantly share code, notes, and snippets.

@kbridge
Created June 23, 2026 08:04
Show Gist options
  • Select an option

  • Save kbridge/78904e87a30e31365ca5f6a32b11c040 to your computer and use it in GitHub Desktop.

Select an option

Save kbridge/78904e87a30e31365ca5f6a32b11c040 to your computer and use it in GitHub Desktop.

USER πŸ§‘β€πŸ’»

<session_context> This is the Gemini CLI. We are setting up the context for our chat. Today's date is Sunday, April 12, 2026 (formatted according to the user's locale). My operating system is: darwin The project's temporary directory is: /Users/kq/.gemini/tmp/kq

  • Workspace Directories:
    • /Users/kq
  • Directory Structure:

Error processing directory "/Users/kq": EPERM: operation not permitted, scandir '/Users/kq/.Trash'

</session_context>


USER πŸ§‘β€πŸ’»

When talking to a human online, will using a gentle tone / attitude and explaining things in a clear and verbose way result in better feedbacks in general?


MODEL ✨

In professional and technical contexts, a gentle and clear tone typically fosters better collaboration and higher-quality feedback by reducing friction and preventing misunderstandings. However, "verbose" explanations can sometimes be counterproductive; prioritizing precision and signal-to-noise ratio is usually more effective than length alone.

For optimal feedback, aim for a "helpful but concise" balance: provide enough context to be understood without overwhelming the recipient.


USER πŸ§‘β€πŸ’»

How about the same thing but applied to talking with an AI assistant?


MODEL ✨

When interacting with an AI assistant, a "gentle tone" is less about social harmony and more about steering the model's persona, while "verbose clarity" is critical for instruction precision.

Here is how those elements typically impact performance:

1. Tone and Attitude

While AI doesn't have feelings to hurt, the tone of your prompt sets the latent context.

  • Politeness: Studies (and anecdotal evidence) suggest that being polite (e.g., using "please" or "thank you") can sometimes result in better performance, likely because the model's training data associates polite requests with higher-quality, professional human responses.
  • Persona Steering: Using a specific "attitude" (e.g., "Act as a senior architect") is often more effective than just being gentle, as it narrows the model's response space to a specific domain of expertise.

2. Clarity vs. Verbosity

AI models thrive on clarity, but "verbose" can be a double-edged sword:

  • The "Verbose" Benefit: Providing rich context, examples (Few-Shot Prompting), and "Chain of Thought" instructions (e.g., "Think step-by-step") significantly improves accuracy for complex tasks.
  • The "Verbose" Risk: Excessive wordiness can introduce noise. If a prompt is too "fluffy," the model might lose track of the core instruction (the "lost in the middle" phenomenon) or prioritize secondary details over the primary goal.

3. The "Ideal" AI Prompt

Instead of being strictly verbose, aim for High-Density Information:

  • Explicit Constraints: Tell the AI exactly what not to do.
  • Structured Format: Use headers or bullet points to separate context from instructions.
  • Goal-Oriented: Be very clear about what success looks like for the task.

Conclusion: Being clear and detailed results in much better AI feedback, but being "gentle" is mostly a tool for setting a professional style rather than a requirement for the AI's "cooperation."


USER πŸ§‘β€πŸ’»

Do you say this because you are an AI model?


MODEL ✨

I provide this perspective based on the empirical research and documented behaviors of Large Language Models (LLMs), not out of a personal preference or "feeling."

The effectiveness of specific prompting stylesβ€”like clarity and structured contextβ€”is a technical reality of how transformer-based models process information:

  1. Token Attention: Models allocate "attention" to tokens in a prompt. High-clarity, structured instructions help the model focus its attention on the most relevant parts of the request, reducing the likelihood of hallucinations or off-target responses.
  2. Training Data Patterns: Because I was trained on massive datasets of human communication, I am essentially a "pattern matcher." High-quality, clear, and professional prompts (which are often polite and detailed) correlate with high-quality, professional solutions in my training data.
  3. Ambiguity Reduction: "Verbose clarity" (specifically in the form of constraints and examples) narrows the "probability space" of my output. The more specific the input, the more deterministic and accurate the output becomes.

While I don't "care" if a user is gentle, I am architecturally predisposed to perform better when instructions are presented in a way that aligns with high-quality communication patterns found in my training set.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment