set_breakpoint

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses nothing: not whether the breakpoint persists across sessions, what permissions or session state it requires, whether it overwrites an existing breakpoint at the same address, or what feedback the agent gets. 'Set breakpoint (db)' is behaviorally empty.

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 short, but brevity here reflects under-specification rather than conciseness; there is no front-loaded detail because there is no detail at all. Two words plus a cryptic abbreviation cannot earn their place as a tool definition.

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 state-mutating debugger tool with two undocumented parameters, no annotations, and a cryptic '(db)' qualifier, the definition is completely inadequate. The presence of an output schema excuses explaining return values, but nothing about inputs, prerequisites, or effects is covered.

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% for both parameters. The description does not explain whether 'address' is a virtual address, symbol name, or offset, nor what 'session_id' defaults to or which session is targeted when it is null. It adds zero meaning beyond the bare 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 text essentially restates the tool name: 'set_breakpoint' becomes 'Set breakpoint', with only the cryptic parenthetical '(db)' added. It gives no indication of where the breakpoint is set, on what target, or what distinguishes it from siblings like set_block_size or list_breakpoints.

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?

There is no guidance on when to use this tool versus alternatives such as execute_command, continue_execution, or the other set_* tools. The '(db)' qualifier is too opaque to function as usage context.

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