cw_mixer_targets

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that a CC reaches SONAR but only applies where a track is listening, and that messages without a destination are delivered and dropped. However, it does not state whether this is a read-only diagnostic, what the response looks like, or any permission or side-effect concerns.

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 with no filler, and the routing problem is introduced up front. It is slightly abstract and lacks an explicit action verb, but it does not waste space.

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?

There is no output schema, so the description would ideally explain what the tool returns. It explains the conceptual routing situation well but leaves the actual result format ambiguous, which is a meaningful gap for a diagnostic tool.

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 takes zero parameters, so there are no parameter semantics for the description to clarify. Baseline 4 is appropriate because parameter coverage is not a relevant gap here.

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 identifies the resource as live MIDI mixer targets and explains the condition under which MIDI CC messages affect tracks. However, it never states the action the tool performs (e.g., 'reports' or 'lists') and does not explicitly distinguish itself from closely related siblings such as cw_mixer_support or cw_midi_cc.

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 phrase 'invisible unless you check' implies the tool is useful for diagnosing silently dropped MIDI messages, giving an implied usage context. But there is no explicit guidance on when to use this tool versus alternatives, and no exclusions or prerequisites are stated.

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