set_breakpoint

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

No annotations are provided, so the description must fully disclose behavioral traits. It mentions the prerequisite of load_elf for symbols, but does not cover other important aspects such as whether a connection is required, whether the target must be halted, or what happens if an invalid address is provided. The description is insufficient for complete transparency.

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 concise, with two sentences for the main purpose and a clear list of arguments and returns. Every sentence adds value, and the structure is front-loaded with the core action.

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 covers the essential steps for setting a breakpoint but lacks details about the broader context, such as the need for a prior connection (connect) or target halted state (halt). Given the complexity of a debugger toolset, it is adequate but not fully comprehensive.

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 add meaning. It provides format examples for address (hex string) and symbol (function name), and explains the dependency on load_elf for symbols. This goes beyond the schema's minimal structure.

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's purpose: setting a breakpoint at a specified address or function name. It specifies that one of address or symbol must be provided, and distinguishes from sibling tools like list_breakpoints and clear_breakpoint.

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 clear usage guidance: it states that either address or symbol must be provided, and notes that using a symbol requires prior loading of an ELF file via load_elf(). This helps the agent understand prerequisites, though it could explicitly state when not to use this tool relative to others.

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