SetBreakpointWithCapture

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

Annotations already declare readOnlyHint=false, idempotentHint=false, and destructiveHint=false, so the agent knows this mutates debug state but is not destructive. The description adds the blocking wait-for-hit semantics, which is useful. However it says nothing about timeout expiry behavior (despite a 10s default timeout_ms), whether the breakpoint persists or is deleted, or what 'structured context' actually contains.

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?

A single front-loaded sentence with zero filler, which is structurally efficient. It is arguably too terse for a 10-parameter tool, but that under-specification is penalized under other dimensions rather than here.

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?

For a 10-parameter debugger mutation with no output schema and zero schema description coverage, one sentence is wholly inadequate. An agent cannot determine what capture is performed, what the JSON blob parameters expect, or what happens on timeout without consulting documentation outside this definition.

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% across 10 parameters, so the description carries the full burden and adds nothing. Parameters like ranges_json, registers_json, expressions_json, stack_slots_json, max_skip_breakpoints, ignore_foreign_breakpoints, and delete_after_hit are completely opaque from name alone, and the description does not clarify any of them.

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 gives a specific verb sequence and resource: set a breakpoint, wait for it to hit, capture structured context. That distinguishes it from DebugDeleteBreakpoint, WaitForPause, and CaptureStopContextStructured reasonably well as a composite one-shot action, though it never explicitly says how it differs from chaining those siblings.

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 on when to use this versus DebugDeleteBreakpoint + WaitForPause + CaptureStopContextStructured, or versus simply setting a breakpoint. There is also no mention of prerequisites such as the debuggee being attached or initialized. The agent must infer the scenario entirely.

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