dsk_off

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

No annotations are provided, so the description carries the full disclosure burden. It conveys the outcome (layer leaves air) but says nothing about whether the configured DSK transition is used, whether other layers are affected, required permissions, or whether the action is reversible.

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?

A single front-loaded sentence with zero filler; the parenthetical acronym expansion is the only addition and it aids comprehension. Nothing could be removed without losing meaning.

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 one-parameter toggle with no output schema and an adjacent dsk_on sibling, the description is nearly sufficient to call the tool correctly. The main missing piece is whether the off-air action uses the layer's transition settings or cuts immediately.

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 description coverage is 100%: the single 'dsk' parameter is documented in the schema with an enum of 1 or 2. The description adds no syntax or value meaning beyond that, which is the expected baseline when the schema does the work.

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 names a specific verb-and-resource ('take a DSK layer off air') and defines the acronym, so an agent knows exactly what state change results. It does not explicitly name the counterpart (dsk_on) or the related dsk_auto, but 'off' versus the sibling names makes the distinction inferable.

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?

Usage is only implied: the verb 'off air' suggests a production-control action for removing a keyer layer from program output. It never states when to prefer this over dsk_auto or dsk_on, nor any prerequisites such as the layer being on air first.

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