memory_update

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

由於未提供 annotations，描述承擔行為揭露的責任。它新增了 token 限制與 overflow 時改用 archive 的行為提示，這些是 schema 未提供的。但未說明 append 與 content 的實際更新行為（附加或覆寫）、auto_summarize 的具體效果，或更新的權限與後果，行為揭露仍有明顯缺口。

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?

工具操作相對簡單，搭配 100% 的 schema 參數說明已足夠使用。描述的 token 限制警告補充了重要的操作情境，並引導至 archive。但缺少輸出格式說明，也未描述更新後的驗證方式，因此略有不足。

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%，每個參數都有明確說明，描述本身未增加額外的參數語意。僅有 token 限制的警告間接關聯 auto_summarize，但未直接解釋參數用法，因此依基線給 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?

描述明確使用動詞「更新」搭配資源「Core Memory」，並指出記錄專案進度和決策的用途。與 siblings 的讀取、搜尋、狀態、封存操作有清楚區隔，且特別提及 memory_archive 作為 overflow 的替代，進一步強化目的區分。

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?

描述明確指出當 Core Memory 超過 ~2000 token 限制時建議改用 memory_archive，提供了具體的使用條件與替代工具。但未說明與 memory_recall、memory_search、memory_status 的使用時機，僅依賴工具名稱本身來暗示更新的用途。

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