breakpoint

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

With no annotations provided, the description carries full burden but only states the action without disclosing side effects, requirements (e.g., connection_id), or what happens when a breakpoint is set or removed. It does not contradict annotations, but provides minimal behavioral context.

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, front-loaded sentence with no wasted words. However, it is under-specified in content, though concise in structure.

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?

Given the tool's 7-parameter complexity and lack of annotations/output schema, the description is insufficient to understand prerequisites (connection_id), return behavior, or how breakpoints integrate with script execution. It does not explain the set/remove lifecycle.

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 input schema has 100% parameter descriptions, so baseline is 3. The description does not add any parameter-level meaning beyond what the schema already provides; the action enum is self-explanatory from the description.

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 'Set or remove' with the resource 'breakpoints', clearly identifying the tool's dual operation. It distinguishes from sibling debugging tools like 'step', 'evaluate', and 'call_stack'.

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?

No guidance is provided on when to use 'set' vs 'remove', or how this tool relates to other debugging tools like 'pause_on_exceptions'. The description lacks any usage context or alternatives.

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