> ## Documentation Index > Fetch the complete documentation index at: https://docs.teamfollowup.ai/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > Use the public API base URL: https://api.teamfollowup.ai/api. > Authenticate public API requests with Authorization: Bearer YOUR_API_KEY. > Use product-owned terms: agents, calls, campaigns, contacts, phone numbers, billing, and configuration. # Update a tool description > Change only the description of one existing in-call tool. If a skill owns the tool, a later skill save may regenerate its description, so edit the owning skill instead. Required API key scope: `agents:write`. ## OpenAPI ````yaml /openapi.yaml patch /api/agent-builder/agents/{id}/tools openapi: 3.1.0 info: title: TFUAI Server API version: 1.0.0 description: >- API reference for the TFUAI SaaS server. All published endpoints are mounted under `/api`. Responses use a standard envelope: `{ "success": true, ... }` on success and `{ "success": false, "error": "..." }` on failure. Product API modules are being launched module by module. This spec currently exposes only contracted public modules. Authenticate public API requests with an API key in the `Authorization` header: `Authorization: Bearer YOUR_API_KEY`. servers: - url: https://api.teamfollowup.ai description: Production API origin. Public API paths are under /api. - url: https://devapi.teamfollowup.ai description: Development API origin. Public API paths are under /api. security: [] tags: - name: Agents description: Manage voice agents, campaigns, workflows, and outcomes. - name: Analytics description: >- Minimal, non-billing performance summary: volume, conversion, and pickup metrics. - name: Calls description: Review calls, test runs, and execution history. - name: Campaign Workflows description: >- What runs after a call lands: for each outcome (booked, opted out, asked for a callback…), an ordered chain of actions — tag the contact, move a pipeline stage, send an SMS, book an appointment. Stored as a graph: `nodes` are the actions, `edges` say what follows what, and `dispositionEntries` maps each outcome to the node its chain starts at. **Pick the narrowest endpoint that does the job.** | To | Call | | | --- | --- | --- | | See what fires per outcome | `GET .../workflow/digest` | Reads as plain text, no graph walking | | Add steps to an outcome | `POST .../outcomes/{outcome}/nodes` | Server derives node ids, edge ids, handles, layout | | Change a message, tag or setting | `PATCH .../workflow` | Merges; carries no graph, so it cannot damage one | | Remove one step | `DELETE .../nodes/{nodeId}` | Also re-links the chain around it | | Author or replace the whole graph | `PUT .../workflow` | Replaces everything you send | `PUT` is the only one that can re-wire, position nodes, build an `if`, save an unconfigured draft, or copy a whole workflow — and the only one that can overwrite a change someone else made after you read it. Use it when you are genuinely authoring the graph, and send `expectedVersion` when you do. For everything else the narrower endpoints are both easier and safer. - name: Contacts description: Contact list, filters, contact call history, and do-not-call actions. - name: GHL description: CRM variables and contact helpers used by agent and campaign setup flows. - name: Phone Numbers description: >- Caller ID pool, number search, assignment, movement, and release endpoints. - name: Power Dialer description: >- Power Dialer queue, lead cadence, callback, parked lead, and campaign schedule endpoints. - name: Projects description: >- Project management endpoints: list, update, disconnect, configure project campaigns, and validate setup. - name: Skills and Tools description: Manage reusable agent behaviors and in-call tool descriptions. - name: Voices description: Voice catalogue endpoints for choosing the voice used by an agent. paths: /api/agent-builder/agents/{id}/tools: patch: tags: - Skills and Tools summary: Update a tool description description: >- Change only the description of one existing in-call tool. If a skill owns the tool, a later skill save may regenerate its description, so edit the owning skill instead. Required API key scope: `agents:write`. operationId: patch-agent-builder-agents-by-id-tools parameters: - name: id in: path required: true schema: type: string minLength: 1 description: Agent id. example: agent_01J2ABCDEF1234567890 requestBody: required: true content: application/json: schema: type: object additionalProperties: false properties: toolName: type: string minLength: 1 description: type: string maxLength: 600 required: - toolName - description examples: default: value: toolName: transfer_call description: Use when the caller asks to speak with a person. responses: '200': description: Tool description updated. content: application/json: schema: $ref: '#/components/schemas/SkillsToolWriteResponse' examples: default: value: success: true tool: name: transfer_call type: transfer_call description: Use when the caller asks to speak with a person. '400': $ref: '#/components/responses/ValidationError' '401': $ref: '#/components/responses/Unauthorized' '403': $ref: '#/components/responses/Forbidden' '404': $ref: '#/components/responses/NotFound' '429': $ref: '#/components/responses/RateLimited' '500': $ref: '#/components/responses/ServerError' security: - ApiKeyAuth: [] x-codeSamples: - lang: bash label: cURL source: |- curl --request PATCH \ --url https://api.teamfollowup.ai/api/agent-builder/agents/{id}/tools \ --header 'Authorization: Bearer YOUR_API_KEY' \ --header 'Content-Type: application/json' \ --data '{ "toolName": "transfer_call", "description": "Use when the caller asks to speak with a person." }' components: schemas: SkillsToolWriteResponse: type: object additionalProperties: false properties: success: type: boolean const: true tool: $ref: '#/components/schemas/SkillsTool' required: - success - tool SkillsTool: type: object additionalProperties: false properties: name: type: string type: type: string description: type: - string - 'null' required: - name - type - description ApiError: type: object description: Standard error envelope returned by the API. properties: success: type: boolean example: false error: type: string description: Short machine-readable error code. example: Unauthorized message: type: string description: Human-readable explanation of the error. example: Authentication required. required: - success - error responses: ValidationError: description: Validation failed / malformed request. content: application/json: schema: $ref: '#/components/schemas/ApiError' Unauthorized: description: Missing or invalid authentication. content: application/json: schema: $ref: '#/components/schemas/ApiError' Forbidden: description: Authenticated but not permitted (role or tenant scope). content: application/json: schema: $ref: '#/components/schemas/ApiError' NotFound: description: Resource not found. content: application/json: schema: $ref: '#/components/schemas/ApiError' RateLimited: description: Rate limit exceeded. content: application/json: schema: $ref: '#/components/schemas/ApiError' ServerError: description: Unexpected server error. content: application/json: schema: $ref: '#/components/schemas/ApiError' securitySchemes: ApiKeyAuth: type: http scheme: bearer bearerFormat: API key description: 'Send your API key as `Authorization: Bearer YOUR_API_KEY`.' ````