update_merchant

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

With no annotations, description carries full burden: lists side effects (immediate effect, customer visibility, irreversibility), API method, and return structure. 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?

Well-structured with clear sections: purpose, usage, API, return, side effects. Front-loaded and every sentence adds value. No 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?

Complete for a simple update tool: covers purpose, behavior, return structure, side effects, and partial update. 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?

Schema coverage is 100% so baseline is 3. Description adds value by reinforcing partial update and listing typical fields (name, email, phone, address), aiding understanding beyond 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?

Clearly states it updates basic merchant data (name, contact info, address) with '[WRITE] 更新商家基本資料.' Distinguishes from sibling tools by focusing on merchant settings. Includes partial update behavior.

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 context: '適合商家資料異動（如搬遷、更名）時同步更新 Shopline 商家設定.' and explains partial update. Lacks explicit when-not-to-use or alternatives, but sufficient for common use.

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