# Text as tool Node

### Overview

The Text as Tool Node converts text content into a tool that can be used by agents. It's particularly useful for providing agents with static information, methodologies, or guidelines that can be referenced during task execution.

Usage cost: 0 credit

### Configuration

#### Settings

1. **Tool Identity**
   * Tool Name\*: Unique identifier for the tool (no spaces)
   * Tool Description\*: Explanation of the tool's purpose and usage
2. **Content Configuration**
   * Tool Content\*: The text content to be provided
   * Supports variables for dynamic content
   * Content is interpolated at runtime

#### Output Ports

* `text_as_tool` (Tool): A structured tool object that:
  * Returns the configured text content
  * Can be used by agent nodes
  * Maintains consistent formatting
  * Supports optional input parameters

### Best Practices

1. **Tool Naming**
   * Use descriptive, unique names
   * Avoid spaces in names
   * Follow consistent naming convention
   * Keep names concise but clear
2. **Description Writing**
   * Be specific about tool purpose
   * Include usage instructions
   * Define input expectations
   * Explain output format
3. **Content Management**
   * Structure content logically
   * Use variables where appropriate
   * Keep content focused
   * Consider agent context

### Common Issues

* Duplicate tool names
* Missing content variables
* Unclear tool descriptions
* Variable interpolation errors


---

# 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.waterflai.ai/studio/studio-builders/flow-components-nodes/text-as-tool-node.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.