ppk2_disconnect

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

Discloses that the tool stops sampling and drops DUT power before releasing the port. Also notes that the next tool call will reopen the port. This provides important behavioral context beyond just 'disconnect', which is critical for a hardware tool.

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 two sentences, both front-loaded with the core action and purpose. Every sentence is useful and there is no waste. It is appropriately sized for the tool's simplicity.

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 zero parameters and an existing output schema, the description covers all necessary context: what it does, when to use it, side effects (drops DUT power, stops sampling), and lifecycle hint (next call reopens). No gaps.

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?

There are no parameters, so the description does not need to add parameter semantics. The baseline of 4 is appropriate as the schema coverage is 100% and there is nothing to explain.

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 that the tool releases the serial port, stops sampling, and drops DUT power. It also provides the purpose: to hand the port to another process or recover from a wedged connection. This distinguishes it from sibling tools like ppk2_configure or ppk2_measure.

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?

Explicitly says when to use: to hand the port to another process or recover from a wedged connection. It also implies that after disconnecting, the next tool call will reopen, which helps the agent understand the lifecycle.

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