Search SearchShopAI's Research Notes blog — data studies, playbooks, and field notes on agentic commerce (AI attribution, MCP, AI catalog accuracy, ChatGPT ads). Returns matching articles with titles, summaries, and URLs. Use when asked what SearchShopAI has written or published about a topic.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Topic or keywords, e.g. 'attribution', 'MCP', 'hallucinated prices' |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate readOnlyHint=true and destructiveHint=false. Description adds that it returns articles with titles, summaries, and URLs, providing useful behavioral context beyond annotations. 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 wasted words. First sentence states purpose and examples, second sentence states when to use. Well-structured and 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 one parameter and no output schema, the description adequately covers input, output, and usage context. No missing critical information.
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?
Only one parameter 'query' with schema description and maxLength. The description provides example values like 'attribution', 'MCP', adding practical guidance beyond the schema.
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 it searches SearchShopAI's Research Notes blog and returns matching articles with titles, summaries, and URLs. It includes example topics like 'attribution', 'MCP', etc., and distinguishes from sibling get_research_note which retrieves a single note.
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 'Use when asked what SearchShopAI has written or published about a topic.' This provides clear context, though it does not list alternatives or when not to use. Sibling tools like search_products or check_compatibility are clearly different.
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.
Most tools have distinct purposes, but there is clear overlap between 'recommend' and the deprecated 'skincare_recommend', and 'shop' as a routing tool could be ambiguous with 'search_products' and 'recommend'. Descriptions help but are not fully disambiguating.
Naming patterns are inconsistent: some use verb_noun (e.g., check_inventory, compare_products), while others are single words (shop) or use a noun prefix (skincare_cart, skincare_recommend). The deprecated duplicate 'skincare_recommend' further disrupts consistency.
14 tools is well within the 3-15 range and covers the necessary functions for a skincare commerce server: product lookup, search, recommendation, comparison, compatibility, inventory, checkout, deals, research notes, and issue reporting. No excess or deficiency.
The tool set covers core commerce workflows: browsing, product details, recommendations, checkout, deals, and compatibility checks. Minor gaps exist (e.g., order history or user profile management) but are outside the apparent scope. The deprecated duplicate is a minor inefficiency.