edb_kill_process

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

Annotations already mark destructiveHint=true, so the description's addition of 'immediately' and 'force-terminating' adds minor context. No mention of side effects on breakpoints or state, but this is acceptable for a simple kill action.

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?

The description is very concise (two sentences plus return type), front-loaded, and clear. It could be slightly more structured (e.g., a note about being terminal), but it is effective and not verbose.

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?

For a simple, parameter-less destructive tool, the description covers the action, immediacy, and return. It is complete enough given the output schema exists. No need for elaborate context.

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 no parameters (schema is empty, 100% coverage). Baseline is 4 for zero parameters. The description does not need to add parameter info and 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 kills the debugged process immediately, using specific verbs 'Kill' and 'force-terminating'. It distinguishes from sibling tools like edb_pause (pause) and edb_restart (restart) by being a terminal action.

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 implies usage for termination but does not explicitly state when to use this over alternatives like pausing or stepping. No when-not or sibling comparisons are provided, leaving the agent to infer context.

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