terminate_debug

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

Annotations indicate destructiveHint: true, but description adds value: it sends DAP terminate request, falls back to forced disconnect, and is graceful. No contradictions. However, it could be more explicit about consequences like state loss.

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?

Four short sentences, each adds value. Front-loaded with main action. No fluff or 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?

Input schema is empty, no output schema. Description covers behavior (graceful, DAP, fallback) adequately. Could mention requirement for active debug session, but it's implied. Fairly complete for a simple tool.

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?

There are zero parameters, so baseline 4. The description does not need to explain parameters, and it does not.

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 the tool terminates the debugged program gracefully, using DAP terminate request with fallback. It distinguishes from stop_debug by specifying 'graceful exit'. The verb 'terminate' and resource 'debugged program' are specific and unambiguous.

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?

Explicitly says 'Use this instead of stop_debug when you want a graceful exit.' Also mentions 'Escape hatch: see the dap-escape-hatch prompt for unwrapped DAP requests.' Provides clear when-to-use and alternative.

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