切換遊戲模式

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

Annotations 已標示 readOnlyHint=false，描述「切換」也與此一致，但描述沒有額外揭露行為特質，例如改動目標遊戲模式後對遊戲的影響、是否需要權限、是否會覆寫既有模式等。idempotentHint=true 和 destructiveHint=false 的含義也未在描述中補充。

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?

此工具雖簡單，但考量到兄弟工具眾多且包含 mc_run_command 這種可能替代的通用指令工具，描述未提供任何使用情境或排除條件；同時也未說明切換遊戲模式的實際行為後果。搭配 annotation 與 output 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 對 target 有提供詳細說明，但 mode 參數只有 enum 沒有 prose 描述；描述中的「survival、creative、adventure 或 spectator」補足了 mode 的語意，且「對象」也暗示了 target 的用途。不過描述並未說明 mode 為必要參數或 target 預設為 @s，因此只算部分補償。

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?

描述明確指出要對目標執行「切換遊戲模式」的動作，並列舉 survival、creative、adventure、spectator 四種模式，語意清楚且涵蓋資源與操作。但未特別與其他兄弟工具（如 mc_player_action 或 mc_run_command）做區隔，因此不到 5 分。

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_run_command、mc_player_action 等替代工具的選擇條件。使用者只能從工具名稱與語意自行推斷用途。

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