set_breakpoint

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

With no annotations provided, the description carries the full burden. It provides valuable behavioral context via the Tcl expression example showing signal path syntax, but fails to disclose what happens when the condition is met (e.g., pauses simulation, triggers callback) or whether the breakpoint persists across checkpoints.

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?

Extremely concise with zero waste. The single sentence purpose statement followed by the Args block provides immediate clarity. Every element serves a specific function.

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?

Appropriate for a 2-parameter tool with an output schema (which handles return value documentation). The description adequately covers both parameters given the schema lacks descriptions, though it could mention breakpoint lifecycle or interaction with sim_run.

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?

Given 0% schema description coverage, the description effectively compensates by explaining that 'condition' expects a Tcl expression format and that 'name' is optional. The example '{/tb/dut/state == 3}' is critical semantic information not present in 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 'conditional breakpoint in the simulation' with a specific verb and resource. It distinguishes from siblings like watch_signal or sim_stop by focusing on conditional halting, though it could clarify how it differs from watch_signal.

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 provided on when to use this tool versus alternatives like watch_signal, sim_stop, or run_debugger_mode. No mention of prerequisites (e.g., requiring an active simulation connection) or when breakpoints are preferable to single-stepping.

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