obs-set-input-deinterlace-field-order

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

No annotations are supplied, so the description carries the full behavioral burden; it does disclose the async-input restriction, which is the most important operational constraint. It omits what happens on a non-async input (error vs no-op), whether deinterlace mode must already be enabled, and whether the change persists or is live-only.

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 no filler; the scope restriction is attached directly to the action. Brevity borders on under-specification rather than padding.

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 mutation tool with no annotations and no output schema, the definition covers the action and the key input-type restriction, and the schema fully documents parameters. It still leaves an agent guessing about error behavior and the interaction with deinterlace mode, which matters for a settings mutation.

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%, including the enumerated fieldOrder values, so the baseline is 3. The description adds no meaning beyond the schema — it does not clarify that inputName and inputUuid are alternative identifiers or which takes precedence.

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?

States a specific verb and resource ('Sets the deinterlace field order of an input'), which is clearly separable from the sibling getter obs-get-input-deinterlace-field-order and from obs-set-input-deinterlace-mode. It does not explicitly name those siblings, so differentiation is inferred rather than stated.

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 parenthetical 'restricted to async inputs only' gives a genuine precondition for calling the tool, which is more than most siblings offer. However, it never contrasts with obs-set-input-deinterlace-mode or explains when field-order adjustment is appropriate versus changing the mode.

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