breakpoint_set

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

No annotations are provided, so the description must carry the full behavioral burden. It specifies the tool sets a line breakpoint and supports conditional/hit-count/logpoint breakpoints, but does not mention side effects (e.g., whether re-setting a breakpoint replaces or duplicates), permissions, or the impact of logMessage (non-breaking). This leaves some ambiguity.

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 a single, well-structured sentence that immediately conveys the tool's core function and supported features. No unnecessary words or repetition. Ideal conciseness.

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 description lacks details on return values (e.g., breakpoint ID or error messages) and does not explicitly clarify execution behavior (e.g., logpoint continues execution). While the schema covers parameter meanings, the description would benefit from mentioning these contextual aspects to be fully self-contained.

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 each parameter is already explained. The description adds a high-level summary ('conditional, hit-count, logpoint') that maps to parameters condition, hitCondition, and logMessage, but it does not provide additional depth beyond the schema. Baseline 3 is appropriate.

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 'Set a line breakpoint in a source file,' distinguishing it from breakpoint_set_function (function breakpoint), breakpoint_set_exception, breakpoint_remove, and breakpoint_list. It also lists supported features (conditional, hit-count, logpoint), reinforcing the tool's specific purpose.

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 use for line breakpoints, naturally distinguishing from sibling tools like breakpoint_set_function or breakpoint_set_exception. However, it does not explicitly state when to use or not use this tool over alternatives, missing an opportunity for clearer guidance.

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