fetchUse this to retrieve the full uneed.best profile of a product returned by search, by its id (the product slug). Same data as get_product, wrapped in the {id, title, text, url} document shape deep research expects.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Product slug returned by search |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate readOnlyHint=true and destructiveHint=false. The description adds information about the return format (document shape for deep research) but does not disclose any additional behavioral traits such as side effects, rate limits, or authorization needs.
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 two concise sentences with front-loaded action ('Use this to retrieve...') and no wasted words.
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 single-parameter tool with good annotations, the description covers the purpose, usage context, and relationship to siblings. It references 'deep research expects' without elaboration, but this is likely acceptable given the tool's simplicity.
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?
Schema description coverage is 100%; the schema already describes the 'id' parameter as 'Product slug returned by search'. The description merely restates this (by its id, the product slug) without adding new semantics.
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 retrieves a full product profile by its slug, and distinguishes from sibling 'search' which returns summaries. It also notes it returns the same data as 'get_product' but in a specific document shape for deep research.
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 description provides context that the tool is used after 'search', mentioning the id is the product slug from search. It references 'get_product' as an alternative but does not explicitly state when to choose one over the other, nor does it list exclusions.
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.
There are two pairs of tools that essentially do the same thing with different output shapes: search/search_products and fetch/get_product. The descriptions try to separate them by use case, but an agent could easily pick the wrong one, making the boundaries unclear.
Tool names mix bare verbs (fetch, search) with prefixed verbs (get_, list_) and include a compound form (search_products). While readable, the naming conventions are inconsistent and lack a single predictable pattern.
With 9 tools, the count is reasonable for the domain, but the redundant pairs (search vs search_products, fetch vs get_product) suggest the set is slightly padded and could be consolidated to around 7 tools.
The server covers the core read operations for a product directory: search, product details, categories, deals, recent launches, trending, and alternatives. Minor gaps exist, such as no direct category browse without search, but overall the surface is sufficient for the stated purpose.