set_task_breakpoint

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

With no annotations, the description must fully disclose behavior. It notes the task-specific trigger and requirement for OS-awareness, but omits side effects (e.g., whether execution halts), persistence, or relationship to other breakpoint types.

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?

Concise and well-structured: purpose line, prerequisite, args, returns. Every sentence adds value; no redundancy.

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?

While parameters are well-described and an output schema exists, the description lacks details on runtime behavior (e.g., does hitting the breakpoint halt execution?) and removal methods. For a 2-param tool with no annotations, it is adequate but not fully complete.

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 description adds rich semantics beyond the schema: 'address' can be an address or symbol name; 'task' can be name, ID, or magic number. This is critical since schema coverage is 0%.

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's purpose: 'Set a task-specific breakpoint that only triggers for a specific OS task/thread.' This distinguishes it from sibling breakpoint tools (e.g., set_breakpoint, set_conditional_breakpoint) by specifying task-specificity.

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?

The description mentions a prerequisite ('Requires OS-awareness to be configured') but does not explicitly state when to use this tool versus alternatives. It lacks guidance on scenarios or exclusions.

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