editor_debug_step_over

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

No annotations are provided, so the description carries full responsibility. It states the action but does not disclose prerequisites (e.g., active debug session), side effects (e.g., execution pause/advance), or what happens if no debugger is active. Minimal behavioral context is given.

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, a single short sentence that immediately conveys the operation. No filler or redundant information.

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 zero-parameter, simple debugger control, the description is adequate but lacks contextual details about when the tool is applicable (e.g., requiring a running debug session) and how it relates to other debug commands. It is not misleading, but it leaves some operational context implicit.

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 zero parameters, so the description does not need to explain parameter semantics. The baseline of 4 applies, and the description adds no unnecessary parameter details.

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 uses a specific verb ('step over') and resource ('current line in debugger'), clearly identifying the action. It distinguishes itself from siblings like editor_debug_step (step into) and editor_debug_continue by specifying the granularity of the operation.

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 during a debugging session but does not explicitly state when to use step over versus alternatives like step into or continue. No exclusions or alternatives are mentioned, leaving the decision to the agent's understanding of debugging concepts.

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