Set Input Audio Sync Offset

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

The description adds no behavioral context beyond what the annotations already declare (readOnlyHint false, destructiveHint false, idempotentHint true). It does not mention that changing the offset affects audio timing, persistence, or any side effects. Since annotations cover the safety profile, the description still fails to add meaningful transparency.

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 short sentence, which is appropriately concise for a simple setter. It is front-loaded with the action, but could have included more details while still being efficient. No wasted words, but it is minimal.

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?

Given the simplicity of the tool, the description is still insufficient for complete guidance. It does not explain what the offset does (e.g., adjusts audio-video synchronization), when it should be applied, or any consequences. With no output schema and minimal annotations, the description leaves the agent inferring behavior from the name alone.

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%, and both parameters have clear descriptions in the schema. The tool description does not mention parameters at all, so it adds no additional meaning beyond the structured schema. Baseline of 3 is appropriate because the schema does the heavy lifting.

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: 'Sets the audio sync offset of an input'. It is specific about the verb and resource, and it distinguishes from the sibling getter tool (obs-get-input-audio-sync-offset). However, it lacks any nuance about scope or constraints beyond the parameters.

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?

No guidance is provided on when to use this tool versus alternatives, prerequisites (e.g., input must exist), or scenarios where this tool is appropriate. The sibling list includes many setter tools, but no differentiation is given.

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