obs-get-input-deinterlace-field-order

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

With no annotations provided, the description carries the behavioral burden. It implies a read-only getter and adds the useful async-only restriction, but it does not describe return values, error behavior for non-async inputs, or how the input is resolved when both identifiers are supplied or omitted.

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 tightly scoped sentence with no redundant wording. The core action is front-loaded, and the parenthetical restriction follows immediately.

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 getter with full schema coverage, the description conveys the basic purpose and the async-only constraint. However, because there is no output schema and no annotations, it leaves open what is returned and how inputName versus inputUuid is handled, making it minimally adequate rather than complete.

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%, so both inputName and inputUuid are already documented by the schema. The description adds no further parameter semantics and does not clarify which identifier should be used or whether one is preferred, so the baseline of 3 is appropriate.

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 states a specific verb and resource: "Gets the deinterlace field order of an input." It also adds the scoping constraint "restricted to async inputs only," which helps distinguish it from the sibling setter and from the related deinterlace-mode getter.

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 supplies a precondition by saying the input must be async, which implies when the tool is applicable. However, it does not explicitly compare this tool with alternatives such as obs-get-input-deinterlace-mode or obs-get-input-settings, nor does it state when not to use it.

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