Create strobe

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

The description details how the strobe works internally: using a square-wave LFO CHOP, Level TOP, Constant TOP, Select TOP, and Null TOP. It explains the relationship between duty and the LFO's bias. Annotations already indicate non-destructive and open-world behavior, and the description adds significant context beyond 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 three sentences, front-loaded with the primary purpose, and every sentence adds essential information without waste. It efficiently covers mechanism, parameters, and output.

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 the complexity (7 parameters, no output schema), the description covers the core functionality, internal components, and outputs (Null TOP). It lacks some fine-grained wiring details but is sufficient for an AI agent to understand and invoke the tool 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?

All 7 parameters have schema descriptions (100% coverage), and the description adds extra technical context (e.g., 'Bias, which rectangularises the square wave' for duty). This adds value beyond the schema without redundancy.

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 builds a beat-syncable strobe/flash layer, a full-frame colour flash that pulses on/off. It uses specific verbs and resources ('Build a beat-syncable strobe / flash layer'), and differentiates it from sibling tools like create_glitch or create_kaleidoscope by specifying the signature VJ strobe effect.

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 explains the basic usage: it outputs a flash that can be composited over an input source if provided, or bare flash otherwise. It also mentions a limitation for v1 (free-running rate) and hints at future beat-lock capability. However, it does not explicitly compare with alternatives or state when not to use this tool.

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