Avery.Software — Native Execution Runtime
RuntimeUse casesPricingHelpBlog
← Back to helpconcept · agents

What NOT to say in an agent description

2 min

Avoid "connect to X" — the wizard treats auth as setup, not a step. Avoid vague pronouns. Avoid stuffing with details.

Three anti-patterns the wizard handles but you can avoid up front:

1. "Connect to my Outlook" as a step. The wizard already knows it needs auth; explicitly listing "connect" as a step used to confuse the older SLM. The current version drops connect-style verbs, but cleaner descriptions read more naturally.

2. Vague pronouns. "Read it and send it" — what's "it"? Be explicit: "Read the unread emails, summarise them, send me the summary."

3. Stuffing every detail into one paragraph. The SLM has a 32K context but lower-end models start losing track around 1500 chars in a single prose blob. Break into short, distinct sentences. One sentence per logical step is ideal.

The wizard's holistic-review pass catches a lot of this, but every problem you avoid up front saves a planning iteration (which costs the SLM 5-10 seconds of compute).


Live recipes need the desktop

This article is a static preview. The in-app Help sidecar inside Avery NXR can fire each step against your live project — install the desktop to use it interactively.

Download desktop →