# Intent & Context

Use **Intent** to say *what* to accomplish. Use **Context** to supply *everything the AI needs to do it safely and correctly*.

### Intent

Describe the goal in natural language. Be direct.

> "Schedule a meeting with John next week"

> "Create a new contact in CRM from the last inbound email"

Good intents are outcome‑focused&#x20;

### Context

Add execution details the agent shouldn’t have to infer or expose to end users. This is a free‑form guidance. Use it to pass:

* Time constraints and windows (`timezone=Europe/Copenhagen`, `window=next_week`)
* Environmental facts and feature flags (`crm=hubspot`, `dry_run=false`)
* Data bindings and IDs the UI shouldn’t show
* Safety constraints / policies (max changes per run, rate limits)
* Additional guidance for edge cases

**Do NOT leak sensitive context to users.** Context is meant for the system/agent, not for display.


---

# Agent Instructions: 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:

```
GET https://docs.toolregistry.ai/concepts/intent-and-context.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
