Connect QLab cue stack

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

Annotations already indicate this is not read-only (readOnlyHint=false) and not destructive (destructiveHint=false), and the description clarifies it creates a scaffold rather than modifying existing entities. However, it does not mention side effects like immediate OSC activation (from the active parameter), external dependencies, or what happens to existing cue stacks.

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 that directly states the action and object. It is concise with no wasted words, though terms like 'status' and 'rehearsal-focused setup notes' are slightly vague.

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 tool with 9 parameters and no output schema, the description is too sparse. It does not explain what a 'scaffold' entails, how OSC networking is configured, whether QLab must be running, what the return value looks like, or why rehearsal-focused notes are included. This leaves significant gaps for an agent to invoke and interpret results 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 schema covers 67% of parameters with descriptions, so the description does not need to repeat them. The phrase 'cue command maps, status, and rehearsal-focused setup notes' adds some sense of what the scaffold produces, but it does not clarify ambiguous parameters like cue_count, send_port, or receive_port, which the schema leaves undocumented.

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 uses a specific verb ('Create') and identifies the resource ('QLab OSC cue-stack scaffold') with added context about contents (cue command maps, status, setup notes). However, the tool title says 'Connect' while the description says 'Create', creating minor ambiguity and not fully distinguishing from sibling tools like qlab_osc_bridge or create_cue_sequencer.

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?

No guidance is provided about when to use this tool versus alternatives such as qlab_osc_bridge or create_cue_sequencer. It describes what it does but gives no context for selection, prerequisites, or exclusions.

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