Create panic control

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

The description goes well beyond the destructiveHint annotation by explaining exactly how Blackout (Level TOP brightness1 = 0) and Freeze (Cache TOP active = 0) are implemented, why it's destructive, and the return value. It also discloses internal construction details (Select TOP, Ramp TOP, Null TOP) that are not in annotations or schema.

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 well-structured paragraph that front-loads the purpose, then systematically explains the mechanics, modes, output, and return values. Every sentence earns its place without redundancy, making it concise despite its length.

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 tool's complexity and lack of an output schema, the description is fully complete: it explains the internal node graph, the two input modes, the destructive consequences, the exposed controls, and explicitly lists the returned node paths and toggle states. No important behavior is left unexplained.

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 input schema already covers all 5 parameters with detailed descriptions (100% coverage). The tool description adds context about how input_path works and the test source, but does not add per-parameter meaning beyond what the schema provides, matching the baseline for high schema coverage.

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 live-performance safety control ('oh no' button) with Blackout and Freeze switches, distinguishing it from generic control creation tools like create_control_surface or create_safety_blackout_chain. The specific verb 'Build' and the detailed COMP structure make the purpose unambiguous.

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 implies a clear use case (live-performance safety) and explains the input_path vs. standalone test source mode. However, it does not explicitly contrast with alternative tools like create_safety_blackout_chain or state when not to use it, so it falls short of full guidance.

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