edb_set_hardware_breakpoint

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

Annotations already indicate non-read-only (readOnlyHint=false) and non-idempotent (idempotentHint=false). The description adds that it uses CPU debug registers, implying limited resource consumption, but does not elaborate on potential conflicts, persistence, or privilege requirements. Some behavioral context is provided, but not comprehensively.

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 reasonably concise, but includes a redundant docstring block (Args/Returns) that largely duplicates the schema. The core sentence is clear, but the structure could be more efficient by front-loading the key points without repetition.

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 complexity (hardware breakpoint, limited registers) and the presence of a good input schema and output schema, the description lacks critical context such as the maximum number of hardware breakpoints, failure scenarios, and the distinction from software breakpoints. It is adequate for basic understanding but not fully complete.

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 description mentions location as 'Address or function name', which adds a bit of meaning, but the input schema already provides detailed descriptions (including examples like '*0x400000' and conditional expressions). With 0% schema description coverage, the description should compensate more; it does not explain the optional condition parameter or provide new insights 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 the tool sets a hardware-assisted breakpoint using CPU debug registers, and mentions specific use cases (ROM, flash, self-modifying code). This distinguishes it from siblings like software breakpoints (edb_set_breakpoint) and watchpoints (edb_set_watchpoint), but it does not explicitly contrast them.

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 suggests when to use the tool (for ROM, flash, or self-modifying code regions), implying it's useful when software breakpoints cannot be applied. However, it lacks explicit guidelines on when not to use it, alternatives, or limitations like the finite number of hardware breakpoints.

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