get_channel_comparison

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

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?

描述以單一重點句開頭，直接點出工具功能（比較各門市/通路的同期業績），第二句補充支援的比較類型。文字精簡、無冗詞贅字，每句皆具備資訊價值，結構前重後輕，易於快速理解。

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?

此工具僅有 2 個參數且 Schema 已完整說明，無輸出 Schema 需要描述補足；描述已涵蓋工具目的、比較維度、使用警示（掃描成本），並在上下文中與眾多分析型 sibling tools 有所區隔。若補充回傳結構或比較對象的選擇方式會更完整，但以現有條件已算充分。

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 對兩個參數的描述已達 100% 覆蓋，且 start_date 特別補充了「逐頁掃描、區間越大越慢」的使用警告，超越 Schema 原本的欄位說明；描述本身也隱含日期區間與比較目的之關聯，因此在 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?

描述以明確動詞「比較」指出工具用途，並具體列出比較維度（營業額、訂單數、客單價）及比較對象（線上 vs 門市、門市之間），能與 sibling tools 如 get_sales_summary、query_orders 明確區隔，聚焦於跨通路比較而非單一彙總或明細查詢。

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?

描述明確說明支援「線上 vs 門市」或「門市之間」的比較情境，讓使用者知道何時採用此工具；雖然未明確列出「何時不該用」或替代工具名稱，但已提供足夠的使用情境脈絡，因此給 4 分。

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.