gdb_disable_breakpoint

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

No annotations provided, but description fully discloses behavior: disabled breakpoints are not hit but remain in the list. No contradictions.

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 sentences, highly concise, no fluff. Action is front-loaded.

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 simple mutation tool, description covers action and side effects. However, no mention of return value or success indication; output schema missing but not critical. Could add brief note on expected outcome.

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?

Parameter descriptions already in schema cover both parameters (session_id and number). Description adds context: session_id comes from gdb_start_session and number is the breakpoint number, reinforcing schema but not adding new semantics.

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?

Clearly states 'Disable a breakpoint by its number without deleting it', specifying the verb (disable), resource (breakpoint by number), and scope (without deletion). Distinct from sibling tools like gdb_delete_breakpoint and gdb_enable_breakpoint.

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?

Explicitly mentions when to use: to disable without deleting, and when to use alternative (gdb_enable_breakpoint for re-enabling). Also notes session_id prerequisite from gdb_start_session.

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