edb_restart

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

Annotations already indicate destructiveHint: true. The description adds behavioral details: the tool kills and restarts, reloads the binary, preserves breakpoints, and returns a status string. This provides useful context beyond annotations. No contradictions.

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 extremely concise: two sentences plus a return type line. Every sentence provides essential information without waste. It is front-loaded with action.

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, no-parameter tool, the description covers the key action and effect (kill, restart, reload binary, preserve breakpoints). The return type is noted. It could mention potential side effects (e.g., loss of runtime state) but overall is adequate.

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?

The tool has no parameters, and schema coverage is 100%. With zero parameters, the baseline is 4, and the description does not need to add parameter information. No further detail required.

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 it 'Kill and restart the debugged program. Reloads the binary, preserves breakpoints.' This is a specific verb (restart) and resource (debugged program), and it distinguishes itself from siblings like edb_kill_process (no restart) and edb_run (does not preserve breakpoints).

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 when a restart is needed, but does not explicitly state when to use this over alternatives like edb_run (which starts from scratch) or edb_kill_process (which only kills). No when-not or exclusionary guidance is provided.

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