gdb_interrupt

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

Description explains that the tool pauses execution, but does not explicitly state if it is non-destructive or what state it leaves the program. With no annotations, this is a moderate disclosure of behavior.

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?

Three sentences cover purpose, usage scenarios, post-interrupt actions, and parameter source. Every sentence is valuable, no fluff.

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?

Given the simple one-parameter tool and no output schema, the description covers usage context and post-interrupt actions adequately. Could mention potential side effects or state safely but overall sufficient.

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?

Parameter schema provides 100% coverage with description 'Session ID from gdb_start_session'. The tool description adds value by linking to sibling tool output, exceeding baseline for full schema coverage.

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?

The description clearly states 'Interrupt (pause) a running program.' It uses a specific verb and resource, and it is distinct from sibling tools like gdb_continue and gdb_next.

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?

The description provides explicit when-to-use scenarios (running, no breakpoint, stuck) and what to do after interrupting (use other GDB commands). It also notes the prerequisite session_id from gdb_start_session.

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