cw_midi_panic

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

With no annotations, the description carries the full burden and clearly discloses the core behavior: all-notes-off, controller reset on every channel, then port reset. It does not mention potential interruptions or confirmation behavior, but the direct effects are transparent and sufficient for a no-parameter panic action.

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 a single, front-loaded sentence with no redundant or filler content. Every clause describes a concrete action, and the sequence of operations is clear.

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 zero-parameter, no-output panic operation, the description covers what is sent and to which scope. The only minor gap is that 'the port' is not further specified, but overall the definition is complete enough for an agent to invoke correctly.

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 tool has zero parameters, so there is no parameter semantics to describe. The schema is empty and fully covered, and the description does not need to compensate for undocumented inputs.

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 states a specific action: send all-notes-off and reset controllers on every channel, then reset the port. This is a clear verb+resource operation that an agent can distinguish from siblings like cw_midi_note or cw_midi_cc. It does not explicitly contrast with another sibling tool, so it stops short of 5.

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 panic semantics imply an emergency reset use case, but the description does not state when to use this tool instead of alternatives such as cw_midi_send or cw_midi_cc. There are no explicit exclusions or conditions, leaving usage to inference from the name and action.

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