reset

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

With no annotations, the description carries the full burden and effectively explains the behavior of each mode, including how conditional breakpoints are handled with 'run'. It adds value beyond the schema.

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 and uses a clear bullet-like format to expose modes. Every sentence adds value, though it could be slightly more structured.

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 reset operation, the description covers modes and conditional breakpoint behavior. However, it lacks prerequisites (e.g., target must be connected) and does not explain the output schema or return value, which is acceptable since an output schema exists.

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 single parameter 'mode' is thoroughly defined in the description with three explicit values and their effects. Since the schema has 0% coverage, the description fully compensates and adds critical 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?

The description clearly states 'Reset the target' and lists three modes with explanations. However, it does not differentiate from the sibling 'halt' tool, which could also be used for halting without reset.

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 provides guidance on when to use each mode (e.g., 'halt' for debugging, 'run' to start running). However, it does not specify when to avoid using reset altogether or compare it to alternatives like 'resume' or 'step'.

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