How to write good Task Descriptions

The Description is where you brief the Task on this specific job. Same Agent, same ground rules - the deliverable, the inputs, the constraints, and what to do with it when it’s done.

What to put in every Description

Four things carry the weight. Everything else is optional.

The deliverable - what you want back, in specific terms
- A 900-word blog draft
- A summary I can paste into Slack
- A shareable link
The inputs - where the Agent should pull from
- My Topic ‘Team Workflows’
- The attached CSV
- The last three posts I published
The constraints - tone, length, format, deadline, anything that would change the shape of the output.
- Match the tone of our published posts
- Under 500 words
- By Monday 9 AM
Where it lands - what should happen with the result.
- Save it to my workspace
- Give me a shareable preview link
- Post it in #marketing

You don’t need all four every time - a research question might not have a “where it lands.” But if you skip all of them, the Agent guesses. And guesses are how you end up with something close.

A weak Description vs a strong one

Weak:

Write a blog post about how small teams work

The Agent doesn’t know how long, what tone, who reads it, or where it goes.

Strong:

Write a 900-word blog post about how small teams manage research. Pull ideas from my saved Topic ‘Team Workflows’, match the tone of my last three published posts, add a hero image, and save the draft to my workspace.

Same idea. But the Agent now has a target, a source, a voice, and a destination.

Write it like a brief, not a prompt

The Description isn’t a chat message. It’s the kind of note you’d leave for a new teammate who’s picking up the work while you step out.

You wouldn’t say “can you write me a blog post?” to a teammate and walk away. You’d tell them who it’s for, how long, what tone, and where to put it when it’s done. The Agent works the same way.