Set Input Deinterlace Field Order

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

Annotations already indicate this is a mutating, idempotent, non-destructive operation. The description adds the specific scope 'asynchronous input' but does not disclose prerequisites, error behavior, or what happens if the input is not asynchronous. It does not contradict 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 a single, front-loaded sentence that directly states the action and target. It contains no filler or redundant information.

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, the description and annotations provide a basic understanding, but the lack of guidance on input identification and the absence of any mention of related getter/set operations make it only minimally complete. No output schema exists, so a bit more context about expected behavior would help.

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 descriptions cover inputName and inputUuid, and the enum for inputDeinterlaceFieldOrder is self-explanatory. The description adds no extra meaning about parameter relationships, such as whether inputName or inputUuid is required to identify the target input, which would be valuable.

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 uses a specific verb ('set') and names the exact resource ('deinterlace field order of an asynchronous input'), which clearly differentiates it from the sibling getter and the related set-input-deinterlace-mode tool. The title and description align and leave little ambiguity about what the tool does.

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?

There is no guidance on when to use this tool versus alternatives. It does not mention the getter for reading the current field order, nor does it explain when setting field order is appropriate or how it relates to other deinterlace settings. The usage context is entirely implied.

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