> For the complete documentation index, see [llms.txt](https://docs.deepwriter.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.deepwriter.com/tips-tricks-and-hacks/prompt-elements/tone-and-style.md).

# Tone and style

Setting the overall voice and feel of your document helps DeepWriter align with your communication goals. The tone influences how the content resonates with your audience.

Let's compare 2 examples:

> <mark style="color:purple;">"Write an essay to clients announcing a new product in a friendly and exciting tone"</mark>&#x20;

versus...

> <mark style="color:purple;">"Compose a legal disclaimer for a software license agreement in a precise and formal tone."</mark>

The first example ensures your announcement feels approachable and generates enthusiasm. The second is all clarity and avoids ambiguity.

{% hint style="info" %}
**Pro tip:** For highly nuanced tones, consider adding a brief description of the persona you want DeepWriter to adopt (e.g., "Act as a seasoned legal counsel, ensuring all language is airtight and unambiguous"). This can further guide it beyond just the "formal" instruction.
{% endhint %}

Finally, you can combine tone with the type of outcome you’re aiming for. For example:

> <mark style="color:purple;">“Write a balanced, analytical white paper on the economic impact of AI automation, intended for government policy researchers.”</mark>

> <mark style="color:purple;">“Compose a technical report for a non-technical board audience, using clear, confident language without jargon.”</mark>

Tone is often what makes the difference between content that just informs and content that truly connects. Don’t be afraid to be intentional and specific. When you clearly define how you want your message to feel, DeepWriter can help you strike exactly the right emotional energy.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.deepwriter.com/tips-tricks-and-hacks/prompt-elements/tone-and-style.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.