edb_reverse_continue

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

Describes the core behavior (backward continuation to breakpoint/event) and a key prerequisite. Does not contradict annotations. Could be enhanced with more detail on failure modes or exact state changes.

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?

Two sentences plus a return type line. Every part is necessary and front-loaded with the primary action. 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?

For a simple tool with no parameters and annotations providing some context, the description covers the main behavioral aspects and return type. It is adequate for an agent to select and invoke correctly.

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?

Tool has zero parameters and schema coverage is 100%, so the description adds no parameter information beyond what is already present. Baseline score of 3 applies.

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 'Continue execution backward to the previous breakpoint or event,' specifying a unique action that distinguishes it from forward continuation and other reverse commands like edb_reverse_step.

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?

Explicit prerequisite: 'Requires GDB recording to be active (target record-full).' Also states 'Useful for rewinding to find where state changed,' implying when to use. No explicit alternatives, but sibling differentiation is implied by action type.

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