> For the complete documentation index, see [llms.txt](https://docs.crobox.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.crobox.com/how-to-guides/sagent/setup/tools.md).
# Tools
Enable optional tools that help shoppers assess and compare products.
The **Tools** section adds optional capabilities to product conversations. Tools are actions Sagent can use when a shopper needs more detail than a recommendation provides.
Enable only the tools that support your buying journey. Test each enabled tool with representative products before publishing.
### How tools appear for shoppers
Tools appear within the Sagent conversation when they are relevant to the shopper's journey. Shoppers do not configure or launch tools themselves.
For example, Sagent can show a review summary or a product comparison at the end of a conversation when results are shown.
Use tools to help shoppers make a decision without leaving the conversation. They provide evidence for a recommendation and reduce the need to search across product pages.
### Product review summary
Enable **Product review summary** when reviews help shoppers evaluate products. Sagent surfaces useful review themes within the conversation.
Use it when review sentiment, common strengths, or common concerns affect a purchase decision.
{% stepper %}
{% step %}
#### Check your review data
Use this tool when product reviews are available and relevant. Keep it disabled when review data is incomplete or unreliable.
{% endstep %}
{% step %}
#### Select the review property
Under **General Tools**, select **Product Reviews Summary**. A new dropdown appears.
Select the product property that contains review information.
{% endstep %}
{% endstepper %}
{% hint style="info" %}
This feature requires a product property containing reviews.
{% endhint %}
### Comparison tool
Enable the **Comparison Tool** when shoppers need to assess similar products side by side.
Sagent shows the comparison in a pop-up during the conversation. It helps shoppers understand meaningful differences without opening several product pages.
{% stepper %}
{% step %}
#### Create a comparison
Set up the properties to compare in **Experiences → Product Comparisons**. See [Create a Product Comparison](/how-to-guides/product-comparisons/create-a-product-comparison.md) for the full setup, including property sections, product filtering, and labels.
{% endstep %}
{% step %}
#### Add the comparison to Sagent
Under **General Tools**, select **Product Comparison**.
Select your comparison from the new dropdown.
{% endstep %}
{% endstepper %}
### Custom tools
Custom tools connect Sagent with functionality built for your specific use case. They can bring new information into Sagent, send information from Sagent to another service, or do both.
For example, a tool can analyze information and return the result to Sagent. It can also send a shopper's request to another system. Sagent can then use any returned information alongside product data and its existing recommendation logic.
Each custom tool connects to a custom tool component. A Crobox team member builds this component outside Sagent. You cannot create it from the **Custom Tools** section.
Before requesting a component, define:
* When Sagent should use the tool.
* What information it receives from Sagent.
* What it returns to Sagent or sends to another service.
When the component is ready, add a custom tool in Sagent. Give it a clear name, select its type, and select the component. Enable the tool when you are ready to test it.
**Example usecases**
Skin-type analysis tool
A skincare retailer can add a tool that analyzes a shopper's uploaded image. The image is sent to the tool. The tool returns a skin type, visible concerns, or both.
Sagent then combines this result with product data. It can recommend products that better match the shopper's needs.
{% hint style="info" %}
Contact your Customer Success Manager to discuss and create a custom tool component.
**This feature is available to advanced and enterprise plans.**
{% endhint %}
### Validate tools before launch
Test each enabled tool in a preview conversation. Check that summaries and comparisons are accurate, relevant, and easy to understand.
{% hint style="info" %}
Enable only tools that improve the shopper's product-selection journey.
{% endhint %}
### Frequently asked questions
When should I enable the comparison tool?
Enable it when shoppers choose between similar products. Ensure the products have consistent, comparable properties.
Should I enable both tools?
Enable each tool only when it supports the catalog and shopper journey. Test their combined experience before launch.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.crobox.com/how-to-guides/sagent/setup/tools.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.