Agent 移動

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

因 annotations 全為 false，描述承擔了行為透明度的責任。它揭露了被方塊擋住時該步會失敗但不會中斷後續，以及每格一條指令的特性，超越了 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?

涵蓋了核心資訊：動作內容、失敗處理、前置條件及方向相對性。雖然未提及回傳值，但輸出 schema 存在，因此足夠完整。

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 描述覆蓋率僅 33% (只有 delayMs 有描述)，描述補充了 steps 代表的格數與 direction 的相對面向語意，有效填補了未描述參數的缺口。delayMs 則由 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?

明確的動詞與資源 (讓 Agent 走 steps 格)，指出是 Agent 專用移動工具，並提及需先召喚，與 mc_agent_teleport 等兄弟工具明顯區隔。

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?

明確指出前置條件 (必須先用 mc_agent_create 召喚)，並解釋方向是相對自身面向而非世界方位，提供實際使用情境。但未直接說明與其他移動方式 (如 teleport) 的比較。

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