browse_catalogThe catalog navigation tree: scents, product types and collections with their ids, for use with list_products.
| Name | Required | Description | Default |
|---|---|---|---|
| lang | No | Language for names and descriptions (default en) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the behavioral burden. It communicates that the result is a navigation tree containing scents, product types, and collections with ids, and the action 'browse' implies a read-only lookup. It does not fully specify tree shape or pagination, but that is minor for this simple catalog browse operation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
One tightly written sentence defines the resource, its content, its ids, and the downstream integration with list_products. There is no filler and all context is front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a tool with only one optional parameter and no returned output schema, the description is sufficient. It tells the agent what the response contains and how to use it for list_products, leaving little to inference.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The lang parameter has 100% schema coverage with an enum and default, so the schema already fully explains the input meaning. The description adds no parameter-specific details, which is acceptable because the schema owns that responsibility.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description names a specific resource—the catalog navigation tree—and enumerates its contents: scents, product types, collections, and their ids. It also differentiates the tool by framing it as a taxonomy source for list_products, which clearly separates it from sibling product-lookup tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
'for use with list_products' gives clear context on the intended workflow: browse the catalog to obtain ids, then pass those ids into list_products. It provides useful guidance without explicitly listing exclusions for search_products or get_product.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clearly distinct purpose: browse_catalog returns the navigation tree, list_products returns products with optional facet filtering, get_product returns full details for a single product, and search_products performs keyword search. There is no meaningful overlap between them.
All tool names follow a consistent snake_case verb_noun pattern: browse_catalog, get_product, list_products, search_products. This makes the API predictable and easy to navigate.
Four tools is a well-scoped size for a read-only catalog server. Each tool serves a distinct and necessary part of the browsing workflow, and no tool feels redundant or missing.
The tool surface covers the core catalog operations: exploring structure, filtering by facet, retrieving details, and searching. There are no obvious dead ends for typical catalog queries, and the read-only scope does not require update or delete operations.