The navigable catalog taxonomy: every public collection with its permalink (for browse_collection), title, and product count, as a tree. Call once to orient; results change rarely.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| collections | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false. The description adds valuable context: 'results change rarely' and 'as a tree,' which go beyond the structured annotations. It does not contradict annotations.
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?
The description is only two sentences, front-loaded with 'navigable catalog taxonomy,' and contains no filler. Every phrase earns its place: the fields returned, the tree structure, and usage guidance.
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?
With zero parameters, rich annotations, an output schema, and low complexity, the description fully covers what the agent needs to know: what the list contains, how to use it, and that it changes rarely. No additional context is necessary.
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 tool has zero parameters, so the baseline is 4. The description adds meaning about the return content (permalink, title, product count) which indirectly helps the agent understand the operation, though no parameter-specific information is needed.
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 clearly states the tool's function: listing every public collection with permalink, title, and product count as a tree. It uses specific verbs and resource scope, and distinguishes itself from sibling tools like browse_collection by indicating it provides the navigable taxonomy.
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?
The phrase 'Call once to orient' provides clear usage context, and 'for browse_collection' indicates how the permalinks are used with a sibling tool. However, it does not explicitly state when not to use this tool or list alternative tools for other purposes, so it falls short of a 5.
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_collection is for deterministic category browsing while search_products is for free-text discovery, and get_product, get_product_images, and price_product each cover a separate aspect of product research. The diamond search is also cleanly separated from catalog product search.
All eight tools follow a consistent snake_case verb_noun pattern: browse_, get_, list_, price_, and search_. Any variability is purely semantic (e.g., list_collections vs browse_collection) rather than a style mismatch.
Eight tools is well-scoped for a made-to-order jewelry e-commerce assistant: taxonomy, product search/browse, product detail, images, pricing, diamond inventory, and store policy information are all covered without redundant or unnecessary tools.
The tool set covers the full shopper journey: discover collections, search products, inspect product details and images, configure and price a product, research diamonds, and find store policies. The deep_link_url from price_product provides an effective handoff to checkout, eliminating any hard dead end.
