gdb_continue

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

無 annotations 輔助，描述僅說明執行continue命令，但未揭露所需前提（程式必須處於暫停狀態）、可能阻塞行為、超時或錯誤情況，以及副作用（如重新開始輸出）。

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覆蓋率100%。描述無需補充參數資訊，根據規則0參數基準分為4。

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?

明確指出工具用於繼續執行被暫停的程式，並等同於GDB的'continue'命令，與大量GDB相關工具共存時仍能區分其核心功能。但未明確與'gdb_continue_background'等兄弟工具做對比。

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?

未提供任何使用時機或替代方案說明，例如僅適用於暫停狀態的程式，或與'gdb_run'、'gdb_start'等的差異完全缺失。

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