set_breakpoint

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

With no annotations, the description carries full burden. It states that a breakpoint is set and returns confirmation, but does not disclose side effects (e.g., whether it halts execution), permissions needed, or constraints like maximum 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 is a clean docstring with front-loaded purpose, followed by parameter details and return note. It is concise, with no extraneous information, and every sentence adds value.

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 simplicity, the description covers purpose, parameters with semantics, and return type. However, it lacks usage guidance relative to the many sibling tools, slightly reducing completeness.

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%, so the description must compensate. It provides detailed semantics for each parameter: address as hex or symbol, type with valid values ('program', 'read', 'write', 'readwrite'), and impl with options ('auto', 'soft', 'hard'), along with examples. This adds significant meaning beyond the schema.

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 breakpoint at the specified address or symbol', which is a specific verb+resource. It distinguishes itself from sibling tools like set_data_breakpoint, set_conditional_breakpoint, etc., which are specialized variants.

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 given on when to use this tool versus the many sibling breakpoint tools (e.g., set_data_breakpoint, set_conditional_breakpoint). The description does not mention contexts, prerequisites, or exclusions.

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