gdb_breakpoint

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

With no annotations, the description should disclose behavioral traits. It only lists actions without explaining side effects, required states (e.g., running GDB), or failure modes. For example, it doesn't clarify what 'list' returns or whether 'delete' requires a number.

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 at one sentence but is a flat list of verbs. It lacks structure to separate different action groups or link to parameters, making it less effective despite brevity.

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 tool has 8 parameters and supports multiple actions, but the description offers no details on how parameters relate to actions, return values (though output schema exists), or usage examples. This is incomplete for an agent to use correctly.

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%, and the description does not explain any of the 8 parameters (action, location, number, condition, temporary, hardware, watch_expr, confirm). It provides no semantic help beyond the terms 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 lists multiple specific actions (add, delete, enable, disable, list, condition, clear) targeting breakpoints/watchpoints, making the tool's purpose clear. However, it does not differentiate these sub-operations or distinguish the tool from siblings like gdb_run_control or gdb_memory.

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 is provided on when to use this tool versus alternatives (e.g., gdb_run_control for execution, gdb_memory for memory). There are no exclusions or context about prerequisites.

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