set_input_deinterlace_mode

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only states the action and parameter meanings. It does not mention side effects, prerequisites (e.g., input must exist), error behavior, or whether the mode change applies immediately to the active output.

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 highly concise: a single actionable sentence followed by a minimal Args block. It is front-loaded, with no unnecessary words or fluff.

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 simple setter with two parameters, the description covers the basic invocation but omits important context such as error conditions, compatibility with input types, and whether the operation is synchronous. No output schema exists, so the description does not need to explain return values, but behavioral details are missing.

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 0%, so the description compensates by listing the allowed mode values (OBS_DEINTERLACE_MODE_*), which is essential for correct invocation. Input_name is only described as 'Name of the input', which adds little beyond the schema's title, but the mode list provides significant semantic value.

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 action ('Set') and the specific resource ('an input') and property ('deinterlace mode'). It distinguishes itself from sibling getters like get_input_deinterlace_mode and other setters by naming the exact property being modified.

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 when to use the tool (when you need to set an input's deinterlace mode) but does not explicitly mention alternatives or exclusion cases. No guidance is given about when to use this versus the getter or related field-order setter.

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