set_data_breakpoint

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

With no annotations, the description fully explains the behavior: triggers on memory access, optional value matching, and returns confirmation. It is honest and clear.

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 and well-structured with Args/Returns sections. The first sentence captures the essence, and each sentence adds value without verbosity.

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 all parameters and the basic action. Given the output schema exists (confirmation string), it is sufficiently complete, though could mention if breakpoints are additive or replace existing ones.

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 adds rich meaning to all 4 parameters beyond the schema (e.g., examples for address, enumerated values for access/data_width, empty meaning for data_value). Schema coverage is 0%, so this is critical.

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 data breakpoint on memory read/write access, distinguishing it from sibling tools like set_breakpoint (code execution) and set_conditional_breakpoint (condition-based).

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 implies usage for memory access breakpoints but does not explicitly contrast with similar breakpoint tools or provide when-to-use/alternatives guidance.

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