DebugStepToLine

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

No annotations are provided, so the description carries the burden; it does contribute the batch-mode exclusion and a "[read-only]" tag. That tag is questionable for an operation that moves the debuggee's execution point, and the description never states the prerequisite of a live stopped session or what happens to the prior execution position.

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 short sentences with the bracketed tags front-loaded and zero filler. Slightly under-specified rather than verbose, but structurally sound.

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?

With 8 parameters, 5 required, and no output schema, the description should at least cover the debug-session precondition and the post-call state (debuggee now stopped at line). It covers the batch-mode caveat but leaves the session prerequisites 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?

Schema description coverage is 100%, so every parameter including the run/jump mode distinction and the detail verbosity is already documented in the schema. The description adds no parameter-level meaning beyond that, making the baseline 3 correct.

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?

States a specific verb pair ("runs or jumps") and a specific target ("the stopped debuggee to a line"), which is concrete enough to distinguish it from DebugStep (step-by-step) and DebugSetStackPosition. It does not name a sibling explicitly, so it stops short of a 5.

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?

"Runs outside batch mode" is a real usage constraint that tells the agent not to call this inside DebugBatchBegin/DebugBatchEnd, which is useful. However, there is no guidance on when to prefer jump vs run (deferred to the schema) and no explicit statement that an active stopped session is required.

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