Create control surface

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

Beyond the annotations (readOnlyHint=false, openWorldHint=true, destructiveHint=false), the description adds meaningful behavioral context: it builds a specific composite, describes fader-to-parameter binding, and notes that cue buttons fire scenes 'instantly or with a crossfade.' This provides transparency about runtime effects without contradicting the annotations.

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 well-structured sentences, front-loaded with the core purpose. It has minor redundancy (repeats faders/buttons behavior), but remains efficient and scannable. Every sentence earns its place, though the second sentence could be tightened.

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 moderate-complexity tool with no output schema, the description covers the constructed result and usage mode. It lacks explicit prerequisites (e.g., that cues must already exist via manage_cue, or that comp_path must be a valid control COMP), leaving minor gaps for an agent invoking the 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?

Schema coverage is 100%, so baseline is 3. The description enriches the parameter understanding by tying `faders` and `cue_buttons` to their live behavior ('faders move their parameters, cue buttons fire scenes') and explains the role of `morph_seconds` via crossfade, adding high-level meaning beyond the schema field descriptions.

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 the tool's function: 'Build a playable performance panel (a Container COMP of visual widgets)' with specific sub-features (vertical faders, cue buttons). It distinguishes itself from siblings by emphasizing 'beyond the parameter dialog' and referencing `manage_cue` for cue recall, making the scope distinct from generic panel creation tools.

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 description gives practical guidance on use: 'Open the container in Perform/Panel mode for a touchable surface' and explains how faders and buttons behave. It implies when to use this tool (live performance panel with cue control) but does not explicitly name alternatives or exclusions, so it falls short of a perfect score.

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