dbgprobe.reset

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

No annotations provided, so description carries full burden. It describes reset behavior per mode: soft resets and resumes, hard resets hardware, halt resets and halts. Could add more about state persistence or prerequisites, but adequate for basic understanding.

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?

Single sentence, well-structured, front-loaded with verb and resource. No superfluous words, earns its place in the description.

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?

No output schema, but description suffices for tool selection. Lacks info on prerequisites (e.g., must be connected) or return behavior, but given sibling tools and context, agent can infer. Could be more complete for invocation.

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 covers mode with enum and default; description adds semantic meaning ('software reset and resume'). Session_id is required but not explained; schema coverage is 50% but description compensates with mode details.

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 it resets the target, with three distinct modes. It distinguishes from sibling tools like halt, go, or step, specifying exactly what this tool does.

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?

It explains when to use each mode (soft, hard, halt) with brief behavior. No explicit when-not-to-use or alternative tools, but the mode descriptions provide sufficient context for selection.

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