debug_set_breakpoints

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

No annotations are provided, so the description carries the full burden. It does not say whether new breakpoints replace or accumulate with existing ones, whether the file must already be loaded in a stopped session, whether line numbers are 1-based, or what happens on an invalid line or missing file — all material for a debugger mutation.

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?

A single front-loaded sentence with no filler, which is structurally clean. However, the brevity is achieved by omitting essentials rather than by tight editing, so it reads as under-specified rather than concise.

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?

The tool has 4 parameters, three required, zero schema descriptions, no annotations, and no output schema. A one-sentence description leaves an agent unable to determine path resolution, session requirements, or breakpoint-replacement semantics before invoking it.

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 0% across 4 parameters. The description only indirectly illuminates 'lines' (line breakpoints) and 'file' (Python source file); it says nothing about sessionId (the target debug session) or cwd (path resolution base), both of which are ambiguous without explanation.

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 ('Set') and resource ('one or more line breakpoints') plus the target ('Python source file'), which is enough to distinguish it from debug_continue, debug_step, or debug_evaluate. It does not explicitly contrast with the closest sibling behaviors, so it stops short of 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?

There is no guidance on when to use this versus alternatives, and no prerequisites stated (e.g., that it requires an active debug session identified by sessionId, or that it should precede debug_launch/debug_attach in a workflow). The agent must infer placement in the debug workflow entirely from the sibling names.

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