searchUse this when a deep research run needs to look up digital tools and products on uneed.best. Same catalog and same relevance ordering as search_products, returned as {id, title, url} documents; pass a result's id to fetch for the full profile. Prefer search_products when you want structured product fields directly.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false. Description adds that it returns `{id, title, url}` documents with same catalog and relevance ordering as search_products, and instructs to pass id to fetch for full profile. No contradictions.
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?
Two sentences, no fluff. Each sentence provides essential information: usage context, comparison with sibling, output format, and follow-up action.
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 simple search tool with one parameter, the description covers purpose, output format, relationship with fetch and search_products. No output schema exists, but description adequately explains return values.
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 coverage is 0% so description must compensate. The single parameter 'query' is implied by 'look up digital tools and products' but not explicitly documented. However, context makes it clear, so minor deduction.
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 purpose: 'look up digital tools and products on uneed.best' and distinguishes it from search_products by noting the returned format and use case. It also explains how to further use results with fetch.
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?
Explicitly says when to use this tool ('deep research run') and when to prefer the sibling search_products ('when you want structured product fields'). Provides clear context for selection.
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.