> For the complete documentation index, see [llms.txt](https://docs.toolregistry.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.toolregistry.ai/concepts/integrations/agent-instructions-for-integrations.md).

# Agent Instructions for Integrations

Declarative, per-integration guidance that tells the agent **when** to call this integration and **how** to use it safely. Keep it outcome‑focused, scope‑limited, and explicit about side effects.

### Why this matters

Agents discover tools dynamically. Clear instructions reduce hallucinated calls, prevent unsafe writes, and keep cost/performance predictable.

<figure><img src="https://2871986476-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FF8EK6M9Sp3cWWNqnvMRL%2Fuploads%2FQyHPxUsYfN3WfSaJ4C7r%2FScreenshot%202025-09-01%20at%2009.46.59.png?alt=media&amp;token=f95f9566-5e31-4530-bced-cfa1955b6ec9" alt=""><figcaption></figcaption></figure>

### How to write good instructions

* **Be declarative**: describe *what to accomplish* and *when to use this integration*, not step-by-step mechanics.
* **Constrain scope**: enumerate allowed capabilities and explicitly forbid risky actions.
* **Name preconditions**: required fields, auth, scopes, and object existence checks.
* **Define side effects**: what gets written/updated; link to approvals if destructive.