Skip to main content
Project tools define callable functions that prompts can use. They live at the project level, so multiple prompts can reference the same tool instead of duplicating schemas in every prompt. Use tools when the model needs information or actions that are outside the prompt itself, such as search, account lookup, order lookup, ticket creation, calculations, or workflow execution.

​
Tool object model

A project tool includes:
  • A title and icon for the library.
  • A description for humans.
  • A function definition for the model.
  • A JSON parameter schema.
  • Project ownership metadata.
  • Folder position.
Prompts reference project tools through a project-tool reference. That reference is captured in prompt editor state and deployment snapshots.

​
Create a tool

1

Open Tools

Open a project and select Tools from the project navigation.
2

Create a new tool

Click New tool. The app creates the project tool and opens the tool editor.
3

Name the function

Use a stable function name that describes the action. Function names should be short, readable, and safe to keep over time.
4

Write the model-facing description

Describe when the model should call the tool, what the tool returns, and any important limits.
5

Define parameters

Add a JSON schema for the tool input. Mark required properties and use enums when values are constrained.
6

Link it to prompts

Open each prompt that needs the tool and attach the project tool in the prompt editor.

​
Function schema guidance

The model sees the function schema, so the schema is part of the prompt.
Schema partGuidance
NameUse an action-oriented name such as search_policies, get_order_status, or create_support_ticket.
DescriptionTell the model when to call the tool and what not to use it for.
ParametersUse explicit fields and simple types. Avoid a single large payload field unless the backend requires it.
Required fieldsRequire the minimum data needed for a valid call.
EnumsUse enums for known values such as region, product, language, or priority.
DescriptionsAdd field descriptions when the model could confuse two fields.
The current prompt tool schema supports function tools and project-tool references. Keep function names stable because deployed prompts and trace review depend on recognizable tool identity. After creating a tool, attach it to every prompt that should be allowed to call it. A tool in the project library is not automatically available to every prompt. When linking a tool, review the prompt instructions:
  • Explain when the tool should be used.
  • Explain what to do when the tool returns no result.
  • Explain whether the assistant should cite or summarize tool data.
  • Explain whether the assistant can answer without the tool.
  • Add evaluator coverage for the tool-use behavior if it is important.

​
Keep references healthy

Deleting a project tool can leave prompts with broken project-tool references. Before deleting a tool:
  • Search the Tools library for linked prompts.
  • Open each linked prompt and remove or replace the tool.
  • Review deployment snapshots that still depend on the tool.
  • Confirm production traces no longer show calls to the old tool.
Prefer deprecating a tool in the description before deletion when production prompts may still reference it.

​
Tool library triage

Use the Tools library to find:
  • Tools with missing descriptions.
  • Tools with unclear function names.
  • Tools linked to many prompts.
  • Tools that have not been updated recently.
  • Tools that are good candidates for consolidation.
Open a tool preview to inspect description, parameters, and schema JSON before opening the full editor.

​
Next steps

Test and debug tools

Use playground runs, traces, and behaviors to debug tool calls.

Build prompts

Attach project tools to prompt drafts.

Traces

Inspect tool call spans and responses.

Behaviors

Find repeated tool-use patterns in production.