edb_set_breakpoint_condition

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

Annotations indicate idempotentHint=true and destructiveHint=false. The description adds that the condition determines when the breakpoint triggers and that setting an empty condition removes it. It also mentions equivalence to a UI button, providing useful behavioral context beyond annotations.

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 three sentences covering purpose, equivalent action, and parameter/return details. It is well-structured with clear sections (Args, Returns) and no unnecessary words.

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 simplicity and the presence of an output schema, the description adequately covers function. It explains condition removal and provides an example, though it lacks error handling or state change details.

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 input schema already contains descriptions for both parameters (number and condition). The description's 'Args' section essentially repeats this information with a minor example. Since schema coverage is high, the description adds limited additional semantic value.

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 'Set or remove a condition on an existing breakpoint' and equates it to EDB's DialogBreakpoints condition button. This is a specific verb+resource that distinguishes it from sibling tools like edb_set_breakpoint or edb_set_breakpoint_ignore_count.

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 that the breakpoint must already exist but does not explicitly state when to use this tool versus alternatives. No guidance on prerequisites or contexts where removing a condition is preferred.

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