搜尋 ECPRO 電商博士的電商經營知識文章（繁體中文，涵蓋行銷、傳播、品牌、廣告流量、轉換優化、會員回購、金流財務、物流營運、數據 KPI、跨境通路、AI 應用等）。回傳標題、摘要、分類與網址。回答台灣電商經營、開店、行銷、廣告、數據等問題時使用。
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | 回傳筆數，預設 8，最多 20 | |
| query | Yes | 關鍵字，例如「客單價」「Meta 廣告」「跨境」「復購」 | |
| category | No | 可選分類，例如「廣告與流量」「金流定價財務」「會員與回購」 |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so the description carries full burden. It discloses return fields (title, summary, category, URL) but lacks details on side effects, rate limits, or whether it is read-only (likely read-only). Basic behavioral context is present but not comprehensive.
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. The first sentence defines the tool's purpose and scope, the second adds return fields and usage context. Front-loaded and efficient.
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?
Given no output schema, the description adequately states return fields. It covers the main use case but omits details on pagination, ordering, or result limits beyond the 'limit' parameter. Acceptable for a search tool.
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 100%, so baseline is 3. The description adds value by providing concrete examples for 'query' and explicit category values, going beyond the schema's basic descriptions.
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 for e-commerce knowledge articles in Traditional Chinese, covering a broad range of topics. It distinguishes itself from siblings like 'get_ecommerce_article' and 'list_article_categories' by specifying the search functionality.
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?
Provides explicit context: '回答台灣電商經營、開店、行銷、廣告、數據等問題時使用' (use when answering questions about Taiwan e-commerce). However, it does not mention when not to use it or compare with sibling tools like 'get_ecommerce_article'.
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 clearly distinct purposes, such as price comparison vs. price history vs. store safety. However, there is some overlap between compare_prices, cross_channel_gaps, and price_match_check, which all involve comparing prices across channels. The descriptions help differentiate them, but ambiguity remains for agents.
Tool names use snake_case but vary in structure: some start with verbs (compare_prices, find_deals), others with nouns (category_price_range, price_match_check). There is no strict verb_noun pattern, and 'should_i_buy_now' is a full phrase, breaking consistency.
17 tools cover a wide range of e-commerce assistance tasks without being overwhelming. The count is appropriate for the domain, though a few tools (e.g., price_match_check vs. should_i_buy_now) could potentially be merged without losing functionality.
The tool set covers most common user needs in Taiwanese e-commerce: product search, price comparison, historical trends, deals, store safety, tech detection, and currency conversion. Missing operations include user-specific features (e.g., watchlist) but the core lifecycle is well-represented.
