breakpoint

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

With no annotations, the description carries the burden of behavioral disclosure. It adds useful context: hardware breakpoints cause 'no code modification', API breakpoints need 'no need to resolve address', conditional breakpoints can use 'log format string instead of breaking', and set_hw is 'useful when scanning for INT3'. These are meaningful behavioral traits beyond the schema. It does not explicitly state that software breakpoints modify code, but this is implied by the contrast with hardware breakpoints.

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 opens with a clear one-line purpose, then uses a structured 'USE X for Y' format to convey usage efficiently. Every sentence provides actionable guidance without redundancy, and it remains compact despite covering many modes.

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 an 8-parameter tool with multiple modes and an output schema, the description covers the main use cases and explicitly contrasts with the closest sibling (breakpoint_on_api_group). It leaves a minor gap in how deletion identifies the target breakpoint (no breakpoint ID parameter is mentioned), but overall it is sufficiently complete for an agent to select and invoke the tool correctly.

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 coverage is 100%, so the baseline is 3. The description adds value by explaining how parameters interact (e.g., api works only with action='set'), giving concrete examples (e.g., condition 'rcx == 0x1000', log format 'VirtualAlloc(size={rdx}, prot={r9:x})'), and clarifying the action meanings. This goes beyond the schema's field descriptions.

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 the tool sets, lists, or deletes breakpoints and lists supported types (software, hardware, memory, conditional, API-by-name). This specific verb+resource phrasing distinguishes it from sibling tools like breakpoint_on_api_group, which is explicitly called out.

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 provides explicit guidance on when to use each action (USE 'set' WITH 'api', USE 'set_conditional', USE 'set_hw', USE 'list') and names an alternative for bulk API groups (breakpoint_on_api_group instead). This gives clear when-to-use and when-not-to-use context.

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