windbg_watch_memory

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

With no annotations, the description does the heavy lifting. It discloses the primary behavior (set breakpoint, log IP/value, optional stack, continue) but omits potential side effects such as breakpoint persistence, interaction with existing hardware breakpoints, or debugger state changes. This is partial 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?

Two concise sentences deliver the essential behavior and a practical rationale. Every word earns its place with no fluff or 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?

The description explains the core functionality well but lacks context about return values, how the logged output is presented, whether the breakpoint is persistent, and how it coexists with other breakpoints. Given the complexity of debugger tooling, these gaps are noticeable.

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 all parameters are documented in the input schema. The description adds minimal extra meaning beyond mentioning 'optional stack' which aligns with log_stack, but does not introduce new semantic details beyond the schema's own 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?

Description clearly states 'Set a hardware data breakpoint that logs IP, watched value, optional stack, then continues.' This is a specific verb+resource+behavior, distinguishing it from generic breakpoint tools by emphasizing the logging and continue behavior.

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 phrase 'Avoids hand-written ba/.printf escaping' implies using this tool instead of manually crafting debugger commands, providing clear context. However, it does not explicitly name alternatives or state when not to use it, leaving room for ambiguity among similar breakpoint tools.

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