edb_breakpoint_commands

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

Discloses ability to run any GDB command including continue, implying potential state changes, and describes non-stopping logging use. Annotations indicate readOnlyHint=false, consistent.

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 plus structured args/returns, front-loaded with key information, 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 tool complexity (breakpoint commands), description explains concept, GDB equivalence, return type, and usage context; annotations and schema complement well.

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 provides detailed parameter descriptions; the description adds the GDB equivalence but does not significantly enhance parameter understanding beyond that.

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 commands to execute when a breakpoint is hit, verb+resource, and distinguishes from siblings like edb_set_breakpoint and edb_execute_gdb_command.

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?

Provides analogy to GDB's `commands` keyword and notes use case for logging without stopping, but does not explicitly mention when not to use or specify alternatives among siblings.

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