send_shop_message

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

無 annotations，描述自行承擔行為揭露責任。清楚列出副作用：無法撤回/修改、客戶即時通知、大量發送需注意頻率限制，並附上 API 路徑與回傳結構，提供相當豐富的上下文。

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?

對一個寫操作工具而言，已涵蓋目的、API、回傳結構與副作用，資訊足以讓 agent 正確使用。未提及錯誤處理或權限需求，但考量單一參數的簡單度，完整度已相當高。

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 對唯一的 message_data 參數描述已達 100% 涵蓋，且包含範例。描述中並未進一步補充參數語義，故依規則給出基準分 3。

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?

明確指出「發送一般商店對話訊息」，以及「非特定訂單的通用訊息」，與兄弟工具 send_order_message 做出區隔。動詞+資源+適用情境清楚，具備明確目的。

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?

說明適用於行銷通知、活動公告、客服主動聯繫等場景，並強調「非特定訂單」，隱含排除了 order-specific 訊息。但未明確提及「當需要發送訂單相關訊息時請改用 send_order_message」，因此略少一分。

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